[Question] 使用容器loader导入报错,提示Unrecognized field "edgelabel_type"

[fenganhao]

Problem Type (问题类型)

gremlin (结果不合预期)

Before submit

• 我已经确认现有的 Issues 与 FAQ 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents)

Environment (环境信息)

• Server Version: latest(Apache Release Version)

• loader Version:1.5.0(Apache Release Version)

Your Question (问题描述)

使用loader批量导入，schema.groovy对边的描述为
schema.edgeLabel("导致")
.sourceLabel("问题原因")
.targetLabel("质量问题")
.ifNotExist()
.create();
报错Failed to load, cause: Unrecognized field "edgelabel_type" (class org.apache.hugegraph.api.schema.EdgeLabelAPI$JsonEdgeLabel), not marked as ignorable (13 known properties: "check_exist", "target_label", "name", "ttl", "source_label", "nullable_keys", "properties", "sort_keys", "id", "frequency", "ttl_start_time", "user_data", "enable_label_index"])
at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 113] (through reference chain: org.apache.hugegraph.api.schema.EdgeLabelAPI$JsonEdgeLabel["edgelabel_type"])
我很疑惑，代码中并没有edgelabel_type。

Vertex/Edge example (问题点 / 边数据举例)

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

[dosubot]

Hey @fenganhao! I'm here to help you with any bugs, questions, or contributions you have regarding the issue you've encountered. Let's work together to resolve this issue.

To resolve the error "Unrecognized field 'edgelabel_type'" when using the loader to import data with the schema definition for edge labels in HugeGraph, ensure that the JSON data being sent to the API includes the field "edgelabel_type" as it is defined in the JsonEdgeLabel class. The JsonEdgeLabel class has a property edgelabel_type of type EdgeLabelType, which should be included in your JSON payload.

Here is an example of how your JSON payload should include the edgelabel_type field:

{
    "name": "your_edge_label_name",
    "edgelabel_type": "NORMAL",  // or "PARENT", "SUB" based on your requirement
    "source_label": "source_vertex_label",
    "target_label": "target_vertex_label",
    // other properties
}

Make sure that the edgelabel_type field is correctly spelled and matches one of the expected values: "NORMAL", "PARENT", or "SUB". If the field is missing or misspelled, it will result in the "Unrecognized field" error ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[fenganhao]

Hey @fenganhao! I'm here to help you with any bugs, questions, or contributions you have regarding the issue you've encountered. Let's work together to resolve this issue.

To resolve the error "Unrecognized field 'edgelabel_type'" when using the loader to import data with the schema definition for edge labels in HugeGraph, ensure that the JSON data being sent to the API includes the field "edgelabel_type" as it is defined in the JsonEdgeLabel class. The JsonEdgeLabel class has a property edgelabel_type of type EdgeLabelType, which should be included in your JSON payload.

Here is an example of how your JSON payload should include the edgelabel_type field:

{
"name": "your_edge_label_name",
"edgelabel_type": "NORMAL", // or "PARENT", "SUB" based on your requirement
"source_label": "source_vertex_label",
"target_label": "target_vertex_label",
// other properties
}
Make sure that the edgelabel_type field is correctly spelled and matches one of the expected values: "NORMAL", "PARENT", or "SUB". If the field is missing or misspelled, it will result in the "Unrecognized field" error [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosu EdgeLabel is used to define the edge type and describe the constraint information of the edge.

The constraint information that EdgeLabel allows to define include: name, sourceLabel, targetLabel, frequency, properties, sortKeys and nullableKeys, which are introduced one by one below.

There is not "edgelabel_type" in edge_groovy

[dosubot]

The error "Unrecognized field 'edgelabel_type'" occurs because the JsonEdgeLabel class in the EdgeLabelAPI expects the edgelabel_type field in the JSON input. This field is used to specify the type of the edge label, such as "NORMAL", "PARENT", or "SUB" ^[1].

If your schema definition in edge_groovy does not include edgelabel_type, you should ensure that your JSON input to the loader does not include this field either. If the field is not needed, it should be omitted from the JSON input to avoid the error. If you do need to specify the type, make sure to include it in the JSON input with one of the valid values.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[dosubot]

To resolve the error "Unrecognized field 'edgelabel_type'" when using the loader to import data with the schema definition for edge labels in HugeGraph, ensure that your JSON payload includes the edgelabel_type field. This field is required by the JsonEdgeLabel class and should be one of the expected values: "NORMAL", "PARENT", or "SUB".

Here's an example of how your JSON payload should include the edgelabel_type field:

{
    "name": "your_edge_label_name",
    "edgelabel_type": "NORMAL",  // or "PARENT", "SUB" based on your requirement
    "source_label": "source_vertex_label",
    "target_label": "target_vertex_label",
    // other properties
}

Make sure that the edgelabel_type field is correctly spelled and matches one of the expected values. If the field is missing or misspelled, it will result in the "Unrecognized field" error ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[imbajin]

@fenganhao Because the loader did not synchronize completely after the client update. Thank you for your feedback, we will sync it ASAP

@Thespica After updating PR/Doc, the current issue can be linked

[Thespica]

Hi @fenganhao , I'm willing to help with this issue!

It looks like we haven't adapted the loader while we import the father sub edge feature at #624

I'm trying to patch up the missing part of loader, but can not reproduce this field. In order to find out how it happened, can you offer a full example to let me reproduce it? Thanks!

[fenganhao]

Thank you for your willingness to help!@Thespica

I'll provide a full example that should help you reproduce the issue.

Here’s what I have so far:
The issue occurs when I use edgelabel in the schema.groovy.
These are two vertex creation statements:

schema.vertexLabel("质量问题")
    .properties("质量问题名称","ID")
    .primaryKeys("ID")
    .ifNotExist()
    .create();
schema.vertexLabel("问题原因")
    .properties("问题原因描述","ID")
    .primaryKeys("ID")
    .ifNotExist()
    .create();

The vertex labels are imported correctly, but when creating the edge:

schema.edgeLabel("导致")
    .sourceLabel("问题原因")
    .targetLabel("质量问题")
    .ifNotExist()
    .create();

I get the error:

Failed to load, cause: Unrecognized field "edgelabel_type" (class org.apache.hugegraph.api.schema.EdgeLabelAPI$JsonEdgeLabel), not marked as ignorable (13 known properties: "check_exist", "target_label", "name", "ttl", "source_label", "nullable_keys", "properties", "sort_keys", "id", "frequency", "ttl_start_time", "user_data", "enable_label_index"]) 
 at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 113] (through reference chain: org.apache.hugegraph.api.schema.EdgeLabelAPI$JsonEdgeLabel["edgelabel_type"]) 

Let me know if you need any further details or clarification. I really appreciate your help on this!

[Thespica]

Hi @fenganhao , sorry that I can not reproduce this issue yet.

Firstly, it looks like the client failed to deserialize the json with edgelabel_type, but we have tested that case https://github.com/apache/incubator-hugegraph-toolchain/blob/4b89c5d8d8a36d6361987d0b3ca248370793fccf/hugegraph-client/src/test/java/org/apache/hugegraph/unit/RestResultTest.java#L228-L245

Secondly, I have tried to reproduce this issue with docker, followed by official guide. Unfortunately, can not reproduce that issue.

Thirdly, can you offer the full logs? including full hugegraph-loader.log and server.log.

Besides, you can try:

1. follow the guide's example, and than switch that to your own case.
2. offer the full struct file and schema file as guide required: https://hugegraph.apache.org/cn/docs/quickstart/hugegraph-loader/#341-%E5%8F%82%E6%95%B0%E8%AF%B4%E6%98%8E

[fenganhao]

Hi @fenganhao , sorry that I can not reproduce this issue yet.

Firstly, it looks like the client failed to deserialize the json with edgelabel_type, but we have tested that case

incubator-hugegraph-toolchain/hugegraph-client/src/test/java/org/apache/hugegraph/unit/RestResultTest.java

Lines 228 to 245 in 4b89c5d

@SneakyThrows
@test
public void testReadEdgeLabel() {
String json = "{\n" +
" "id" : 14,\n" +
" "name" : "created",\n" +
" "edgelabel_type" : "NORMAL",\n" +
" "links" : [ {\n" +
" "person" : "software"\n" +
" } ],\n" +
" "frequency" : "SINGLE",\n" +
" "sort_keys" : [ ],\n" +
" "nullable_keys" : [ ],\n" +
" "index_labels" : [ ],\n" +
" "properties" : [ "date" ],\n" +
" "status" : "CREATED",\n" +
" "enable_label_index" : true\n" +
"}";
Secondly, I have tried to reproduce this issue with docker, followed by official guide. Unfortunately, can not reproduce that issue.

Thirdly, can you offer the full logs? including full hugegraph-loader.log and server.log.

Besides, you can try:

1. follow the guide's example, and than switch that to your own case.
2. offer the full struct file and schema file as guide required: https://hugegraph.apache.org/cn/docs/quickstart/hugegraph-loader/#341-%E5%8F%82%E6%95%B0%E8%AF%B4%E6%98%8E

@Thespica Thank you very much for your help. Following your advice, I checked the docker-compose.yml file and discovered that the issue was caused by using the latest version for the server image, while the loader image was using version 1.5.0, leading to a version mismatch.

The issue has now been resolved. Thanks again for your support!!!!

[Thespica]

Hi @fenganhao , I tested that the latest server(via docker) still work. I wonder if there is a potential bug, so can you provide more details about the version to let us check that?

[github-actions]

Due to the lack of activity, the current issue is marked as stale and will be closed after 20 days, any update will remove the stale label