You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hugegraph.apache.org by "linmengmeng-1314 (via GitHub)" <gi...@apache.org> on 2026/05/20 09:30:28 UTC
[I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
linmengmeng-1314 opened a new issue, #3032:
URL: https://github.com/apache/hugegraph/issues/3032
# Issue Draft: HBase Backend - Edges Cannot Be Persisted
## Environment
- HugeGraph: 1.7.0 (server), pyhugegraph: 1.7.0 (client)
- HBase: 2.1.2
- ID Strategy: `PRIMARY_KEY`
- Serializer: `binary`
## Description
When HugeGraph uses HBase as the backend storage, **edges cannot be persisted** regardless of the creation method used (REST API or Gremlin). Vertex creation works, but all edge creation approaches either fail explicitly or silently discard the data.
## Reproduction Steps
### Schema Setup
```groovy
// Property keys
schema.propertyKey('name').asText().ifNotExist().create()
schema.propertyKey('date').asText().ifNotExist().create()
// Vertex label with PRIMARY_KEY strategy
schema.vertexLabel('person').properties('name').usePrimaryKeyId().primaryKeys('name').ifNotExist().create()
// Edge label
schema.edgeLabel('roommate').sourceLabel('person').targetLabel('person').properties('date').nullableKeys('date').ifNotExist().create()
```
### Create Vertices
```groovy
// REST API - works fine
POST /graphs/{graph}/graph/vertices
{"label": "person", "properties": {"name": "Alice"}}
{"label": "person", "properties": {"name": "Bob"}}
```
Response IDs: `"1:Alice"`, `"1:Bob"` (composite format from PRIMARY_KEY strategy).
### Attempt Edge Creation
**Method 1: REST API with returned composite IDs — fails with error**
```
POST /graphs/{graph}/graph/edges
{"label": "roommate", "outV": "1:Alice", "inV": "1:Bob", "properties": {"date": "2024"}}
→ 400 Bad Request: IllegalArgumentException: Invalid vertex id '1:Alice'
```
**Method 2: REST API with actual stored IDs (from g.V().id()) — also fails**
`g.V().id()` returns integers (e.g., `9988829793`) instead of the composite IDs returned by addVertex. Using these:
```
POST /graphs/{graph}/graph/edges
{"label": "roommate", "outV": 9988829793, "inV": 9837833573, "properties": {"date": "2024"}}
→ 400 Bad Request: IllegalArgumentException: Invalid vertex id '9988829793'
```
Note: The vertex CAN be retrieved via REST API `GET /vertices/9988829793` (returns 200), but edge creation rejects the same ID.
**Method 3: Gremlin addE — appears to succeed but data is not persisted**
```groovy
g.V().hasLabel('person').has('name','Alice').addE('roommate').to(__.V().hasLabel('person').has('name','Bob')).property('date','2024')
```
Response: Returns the edge object with ID and properties (appears successful).
Verification:
```
g.E().count() → returns stale/incorrect count (e.g., 3)
g.E().toList() → returns [] (empty, correct)
GET /graph/edges → {"edges": []} (empty)
```
The edge is created in memory but **not persisted to HBase**.
## Additional Observations
### 1. Vertex ID Mismatch
With `PRIMARY_KEY` strategy and HBase backend:
- `addVertex` REST API returns composite IDs: `"1:Alice"`
- `g.V().id()` returns auto-generated integers: `9988829793`
- `g.V().valueMap(true)` returns the integer ID
- The vertex is accessible via `GET /vertices/{integer_id}` but NOT via `GET /vertices/1:Alice`
- `g.V({integer_id})` lookup also returns empty (cannot find vertex by its own ID)
### 2. Vertex ID Collision Across Labels
Different vertex labels with different primary key values may share the same internal ID:
```
person:James (pk="James") → stored as 9837833573
webpage:James的个人网站 (pk="James的个人网站") → also stored as 9837833573
```
This suggests the HBase backend generates IDs based on a hash that ignores the vertex label, causing cross-label collisions.
### 3. g.E().count() Returns Incorrect Results
After Gremlin `addE` calls that don't persist:
- `g.E().count()` may return a non-zero stale count
- `g.E().toList()` returns empty (correct)
- REST API `/edges` returns empty (correct)
## Expected Behavior
- Edge creation via REST API should find vertices by the IDs returned by `addVertex`
- Edge creation via Gremlin `addE` should persist edges to the backend
- `g.V().id()` should return IDs that can be used for subsequent lookups and edge creation
- Vertex IDs should be unique across different vertex labels
## Actual Behavior
- No method of edge creation works with HBase backend
- Vertex IDs are inconsistent between `addVertex` response and `g.V().id()`
- Vertex IDs collide across labels
- `g.E().count()` returns stale/incorrect counts
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@hugegraph.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #3032:
URL: https://github.com/apache/hugegraph/issues/3032#issuecomment-4497984883
<!-- Answer -->
Glad to hear the issue is resolved! Thanks for confirming and documenting the fix clearly — this will be helpful for others who encounter the same problem with HBase backend configuration. The `backend=hbase` + `serializer=hbase` pairing is indeed a critical requirement that's easy to miss, especially since other backends like RocksDB do use `serializer=binary`.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fhugegraph).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fhugegraph).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fhugegraph&message_id=eae016af-19c0-4ff4-928b-d9962d847d72) [](https://github.dosu.com/apache/hugegraph?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fhugegraph) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fhugegraph)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For additional commands, e-mail: issues-help@hugegraph.apache.org
Re: [I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
Posted by "linmengmeng-1314 (via GitHub)" <gi...@apache.org>.
linmengmeng-1314 commented on issue #3032:
URL: https://github.com/apache/hugegraph/issues/3032#issuecomment-4496806577
## Additional Environment Details
The issue was reproduced in a Docker deployment environment:
- **HugeGraph Server**: Docker image `hugegraph/hugegraph` (latest from Docker Hub), ARM64 architecture
- **HBase**: Docker image `dajobe/hbase:2.1.2`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For additional commands, e-mail: issues-help@hugegraph.apache.org
Re: [I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
Posted by "linmengmeng-1314 (via GitHub)" <gi...@apache.org>.
linmengmeng-1314 commented on issue #3032:
URL: https://github.com/apache/hugegraph/issues/3032#issuecomment-4497982138
## Resolution
This issue has been resolved by changing the serializer configuration from `binary` to `hbase`.
**Before (broken):**
```properties
backend=hbase
serializer=binary
```
**After (working):**
```properties
backend=hbase
serializer=hbase
```
After switching to `serializer=hbase`, both vertex and edge data can be imported normally. This confirms that the root cause was the incorrect serializer setting, as pointed out by @dosubot above.
**Note:** Existing data written with the binary serializer is incompatible with the hbase serializer format, so a clean re-initialization is required after changing the configuration.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For additional commands, e-mail: issues-help@hugegraph.apache.org
Re: [I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #3032:
URL: https://github.com/apache/hugegraph/issues/3032#issuecomment-4496920471
<!-- Answer -->
The symptoms you're describing — edges not persisting, vertex ID format mismatches between `addVertex` response and `g.V().id()`, and ID collisions across labels — are very likely caused by using `serializer=binary` with `backend=hbase` in your configuration.
**Root cause:** The HBase backend requires `serializer=hbase`, not `serializer=binary` [[1]](https://github.com/apache/hugegraph/issues/1590#issuecomment-907602303). The `HbaseSerializer` extends `BinarySerializer` but critically sets `keyWithIdPrefix=false`, storing IDs in rowkeys rather than column names — a fundamental architectural requirement for HBase [[2]](https://github.com/apache/hugegraph/blob/9126c80e414c073b60fc074361b211cfb409e0eb/hugegraph-server/hugegraph-hbase/src/main/java/org/apache/hugegraph/backend/store/hbase/HbaseSerializer.java). Using the wrong serializer breaks vertex ID encoding and edge serialization/deserialization.
**Fix:** Update your graph configuration to use:
```properties
backend=hbase
serializer=hbase
```
[[3]](https://github.com/apache/hugegraph/blob/9126c80e414c073b60fc074361b211cfb409e0eb/hugegraph-server/hugegraph-dist/src/assembly/travis/start-server.sh#L36-L39)
After changing the serializer, you'll need to clear existing data and re-initialize, since data written with the binary serializer is incompatible with the hbase serializer format.
**Additional HBase configuration reference** [[4]](https://github.com/apache/hugegraph/blob/9126c80e414c073b60fc074361b211cfb409e0eb/hugegraph-server/hugegraph-dist/src/assembly/static/conf/graphs/hugegraph.properties#L46-L56):
```properties
backend=hbase
serializer=hbase
hbase.hosts=localhost
hbase.port=2181
hbase.znode_parent=/hbase
hbase.threads_max=64
```
This misconfiguration is a recurring issue that has been reported across multiple HugeGraph versions (0.11.2 through 1.7.0) with the same symptoms: vertices appear to work but edges fail to parse or persist [[5]](https://github.com/apache/hugegraph/issues/1730#issuecomment-1016032238).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fhugegraph).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fhugegraph).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fhugegraph&message_id=97584a9d-b552-4cd4-bfd3-9f5d0b6d3a1e) [](https://github.dosu.com/apache/hugegraph?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fhugegraph) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fhugegraph)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For additional commands, e-mail: issues-help@hugegraph.apache.org
Re: [I] HBase backend: edges cannot be persisted and vertex ID mismatch [hugegraph]
Posted by "imbajin (via GitHub)" <gi...@apache.org>.
imbajin commented on issue #3032:
URL: https://github.com/apache/hugegraph/issues/3032#issuecomment-4505480110
> ## Resolution
> This issue has been resolved by changing the serializer configuration from `binary` to `hbase`.
>
> **Before (broken):**
>
> backend=hbase
> serializer=binary
> **After (working):**
>
> backend=hbase
> serializer=hbase
> After switching to `serializer=hbase`, both vertex and edge data can be imported normally. This confirms that the root cause was the incorrect serializer setting, as pointed out by [@dosubot](https://github.com/dosubot) above.
>
> **Note:** Existing data written with the binary serializer is incompatible with the hbase serializer format, so a clean re-initialization is required after changing the configuration.
Thanks for the feedback, could also ask [DeepWiki](https://deepwiki.com/apache/hugegraph) for any basic question first
Could close this issue if it was solved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@hugegraph.apache.org
For additional commands, e-mail: issues-help@hugegraph.apache.org