[BUG] g.graphlearn()/g.gremlin() should check if the type is compatible first · alibaba/GraphScope#1509

(2 comments) (0 reactions) (0 assignees)HTML (2,401 stars) (301 forks)batch import

component:pythonenhancementgood first issue

説明

Describe the bug

GraphLearn has implies int64_t as OID_T (see types.h) and current gremlin engine doesn't support string oids as well (see https://github.com/alibaba/GraphScope/issues/1265).

An exceptions should be thrown in g.graphlearn()/g.gremlin() is the oid type of vineyard graph is not compatible with those two engines.

技術スタック: cpp
領域: backend
Issue 種別: bug
難度: 2
推定時間: under 1 hour
活動状況: stale
明確さ: clear
前提条件: basic C++understand OID typesfamiliarity with GraphScope codebase
初心者向け度: 80
調査方針: Investigate the g.graphlearn() and g.gremlin() functions in the GraphScope codebase to identify where to add the type compatibility check. Refer to the types.h file (graphlearn/core/graph/storage/types.h) which defines OID T as int64 t. The exception should be thrown when the vineyard graph's OID type is not compatible. Also consider checking the linked issue #1265 for context on gremlin engine limitations. The fix should be localized and throw an appropriate error message.