JanusGraph / JanusGraph/janusgraph

coding problem with htable

Open
#941 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
5.8k
Forks
1.2k
Avg merge
13h 53m
Merged PRs (30d)
6

Description

hbase:1.2.6
solr:7.4

The data stored in hbase inside, open the hbase table, I would like to know hbase janus inside the storage structure and found to be garbled, I do not know if janus is not done a special conversion
```
JanusGraph graph = JanusGraphFactory.open("\\resources\\janusgraph-hbase-es.properties");
JanusGraphTransaction tx = graph.newTransaction();
final Vertex point_a = tx.addVertex("name","Apoint");
final Vertex point_b = tx.addVertex("name","Bpoint");
point_a.addEdge("knows",point_b,"weight",1.0f);
```
query hbase
```
for (Result result : scanner) {
System.out.println("============ \n rowKey : " + new String(result.getRow()));
for (KeyValue kv : result.raw()) {
System.out.println("***********");
System.out.println("ColunmFamily : " + new String(kv.getFamily(),"utf-8"));
System.out.println("value : " + new String(kv.getValue(),"utf-8"));
// Bytes.toString() also the same
System.out.println("qualifer : " + new String(kv.getQualifier(),"utf-8"));
System.out.println("timestamp : " + kv.getTimestamp());
}
}
```
the result is
```
============
rowKey : 
***********
ColunmFamily : e
value : �
qualifer : 
timestamp : 1519783348260001
***********
ColunmFamily : e
value : �rtnam��
qualifer : �
timestamp : 1519783348260001
***********
ColunmFamily : e
value : � � ��
qualifer : €
timestamp : 1519783348260001
***********
ColunmFamily : e
value : ��� ��
qualifer : €
timestamp : 1519783348260001

```
If I use the normal hbase shell to create the table, encoding no problem, but with janus create a table, there was a coding problem

Contributor guide

Open the contributing guide

Research direction

Start with the Java snippet that opens JanusGraph and writes vertices and an edge, then reproduce the HBase scan shown in the issue. Determine whether the non-readable row keys, qualifiers, and values are expected binary storage or indicate an encoding defect; done means documenting the expected representation or isolating a reproducible conversion problem.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.