GFQL Cypher: current LDBC IC3/IC5 official read-shape residuals
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 20/100
調査の方向性
Start with the pinned official IC3 and IC5 query files in pyg-bench and minimize each query to its first unsupported construct. The probes identify IC3 whole-row carriers (countryX, countryY, person) and IC5 entity aggregation, relationship multiplicity, and later forum scope as barriers. Determine whether to support these shapes or document a capability boundary; done requires preserving campaign status until that decision and keeping dataset conformance and timing work separately gated.
索引モデルが issue の本文から書いたものです。
説明
Current evidence
Current product master 9c2e88855619fffa25d330593f33888c79bc34d7 rejects the pinned official IC3 and IC5 read queries before execution:
- IC3 (
interactive-complex-3.cypher):GFQLSyntaxError— current compiler says only the alternatingMATCH ... WITH ... MATCHread shape is supported. - IC5 (
interactive-complex-5.cypher):GFQLValidationError— current row lowering says it supports oneMATCHsource alias at a time and points to #1273. - Query text and parameters are source-pinned in pyg-bench main
80c49f672d29fd2323cf9e4319b34ffa7dad87ad. - These are current-status probes, not a rerun of the historical May #999 measurements.
The equivalent narrow synthetic IC3/IC5 adapter/GFQL workaround passes all six typed positive/empty-or-negative cases on pandas, Polars, DGX cuDF, and Polars-GPU. That is an adapter route, not dataset conformance proof.
Scope
Do not reopen #999 or #1273: their admitted shapes were completed. Track these separately as the remaining official benchmark shapes.
Acceptance
- Minimize each official query to the first unsupported construct.
- Decide whether each is a parser/read-shape gap, lowering gap, or expected decline with a documented capability boundary.
- If supported, add focused positive/negative row-oracle tests and clarify the misleading stale residual message.
- Preserve current IC3/IC5 campaign status until these are resolved or explicitly declined.
- Keep dataset conformance and timing/comparison work separately gated.
2026-10-26 exact-master feasibility update
On pygraphistry master d53fba85532949fd8881d6cb8079ebbdf17cb111, pyg-bench main 80c49f672d29fd2323cf9e4319b34ffa7dad87ad, and pinned official IC3/IC5 query files, bounded throwaway probes classified deeper barriers without retaining a product patch:
- IC3: relaxing only the parser and compile-time suffix-
WITHcaps lets a minimal two-reentry shape compile and return the hand-computed positive row[{"a.id":"a"}]and empty negative row. The full official query then declines becausecountryX,countryY, andpersonare non-source whole-row carriers. A parser-only relaxation does not make IC3 runnable. - IC5: allowing the first aggregate-only alias guard advances
collect(friend)to the relationship-multiplicity guard; a further throwaway relaxation reaches lostforumscope after the later suffix. #1273's closed scalar/disjoint-source cases do not establish support for this entity-aggregate carrier. A correct implementation must preserve node identity, relationship multiplicity, and later scope together.
The product source was restored clean after these probes. Keep both official shapes as typed capability declines and this issue OPEN. Reassess implementation when a real MCP workflow needs them or a bounded generalized design can pass positive/negative row, multiplicity, and pandas/Polars/cuDF/Polars-GPU parity gates. Synthetic adapter/GFQL parity and separate SF0.1 dataset-backed adapter probes do not certify literal official Cypher or competitive timing.
- 主要言語
- Python
- スター
- 2.6k
- フォーク
- 229
- 平均マージ
- 1日 5時間
- マージ済み PR（30日）
- 99
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
graphistry/pygraphistry のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
graphistry/pygraphistry#2171 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
graphistry/pygraphistry#1965 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
graphistry/pygraphistry#1208 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
graphistry/pygraphistry#966 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
graphistry/pygraphistry#824 ·
メンテナーはふだん 1 日以内に返信
graphistry/pygraphistry の issue をすべて見る
似ている issue
-
Import errors are swallowed: PerthImplicitWatermarker silently becomes None対応中かも @JonRC が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
resemble-ai/Perth#23 ·
-
correction metadata
難易度 2/5 1時間未満 初心者へのやさしさ 65/100
acl-org/acl-anthology#10753 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
earthtojake/text-to-cad#758 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 70/100
DataTalksClub/faq#545 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信