Hi all, Following up on GitHub issue #1783, I've been implementing a first-party LlamaIndex integration for Apache AGE. It implements LlamaIndex's modern PropertyGraphStore API (the same abstraction the Neo4j, Memgraph, and Kuzu integrations use), rather than the legacy triplet-based GraphStore. Current status: A graph-only v0.1, written as a thin adapter over psycopg3.Implements the PropertyGraphStore contract: upsert_nodes, upsert_relations, get, get_rel_map, delete, and a read-only structured_query.Has a unit test suite plus a live PostgreSQL + Apache AGE integration suite, both currently passing, along with a CI workflow.Vector support is intentionally deferred to a later v0.2.Before I open a pull request, I'd like the PMC's guidance on two governance questions so this lands in the right place: Where should the integration live?(a) In-tree in apache/age under a new integrations/ directory, or(b) a separate repository (e.g. an apache/age-* repo, or a community-maintained one).Is there a preference or existing precedent for where AGE integrations should be hosted? PyPI publishing and ownership.To be pip-installable (the point of a first-party integration), the package would be published to PyPI as "llama-index-graph-stores-age". Should that release be owned and published under the ASF, or maintained externally? I want to confirm this up front because of the "AGE" naming (Apache trademark) and the release cadence, rather than reserve the name in the wrong place. Once the preferred home is confirmed, I'm happy to open the PR and walk through the design, tests, and CI. I can also share more detail on the list if that's helpful. Thanks for your time,Prashant Chinnam GitHub: @crprashant
