incorvia commented on issue #1705: URL: https://github.com/apache/age/issues/1705#issuecomment-2169488596
> My number one reason is because AGE is built on top of Postgres. Most of our relational data is already in Postgres so AGE enables the combination of SQL and Cypher, very powerful. > > The biggest challenge I'm having with AGE is trying to extend AGE with search capability. I'm using ParadeDB's `pg_bm25` extension but it can't index AGE's `agtype` data. My ultimate goal is to integrate AGE with LLM but it needs searching capability(both bm25 and vector search). > > For reference, these are the use cases I need. https://neo4j.com/blog/unifying-llm-knowledge-graph/ New to all this so forgive me if this question reveals my naivety, but what's stopping you from indexing your data using something like ElasticSearch or Solr? Is it that you are trying to use Postgres as a one stop shop? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
