After bringing up neo4j and then running embabel-guide and loading the data: curl -X POST http://localhost:1337/api/v1/data/load-references, querying the guide resulted in
Failed to invoke proceduredb.index.vector.queryNodes: Caused by: java.lang.IllegalArgumentException: There is no such vector schema index: embabel_content_index at org.neo4j.driver.internal.util.Futures.blockingGet(Futures.java:63) at org.neo4j.driver.internal.InternalResult.blockingGet(InternalResult.java:116) at org.neo4j.driver.internal.InternalResult.list(InternalResult.java:85) at org.drivine.connection.Neo4jConnection.query(Neo4jConnection.kt:44) at org.drivine.manager.NonTransactionalPersistenceManager.query(NonTransactionalPersistenceManager.kt:33)
This is because the guide was asking for embabel_content_index and the index loaded was: embabel-content-index
The indexes had to be dropped and rebuilt:
DROP INDEX embabel-content-index; CREATE VECTOR INDEX embabel_content_index FOR (c:Chunk) ON (c.embedding) OPTIONS {indexConfig: { vector.dimensions: 384, vector.similarity_function: 'cosine' }}
One or the other must be the source of truth - either embabel-hub is correct and the indexes loaded in must change or the loaded indexes are correct and embabel-hub must reference them.
After bringing up neo4j and then running embabel-guide and loading the data:
curl -X POST http://localhost:1337/api/v1/data/load-references, querying the guide resulted inFailed to invoke proceduredb.index.vector.queryNodes: Caused by: java.lang.IllegalArgumentException: There is no such vector schema index: embabel_content_index at org.neo4j.driver.internal.util.Futures.blockingGet(Futures.java:63) at org.neo4j.driver.internal.InternalResult.blockingGet(InternalResult.java:116) at org.neo4j.driver.internal.InternalResult.list(InternalResult.java:85) at org.drivine.connection.Neo4jConnection.query(Neo4jConnection.kt:44) at org.drivine.manager.NonTransactionalPersistenceManager.query(NonTransactionalPersistenceManager.kt:33)This is because the guide was asking for embabel_content_index and the index loaded was: embabel-content-index
The indexes had to be dropped and rebuilt:
DROP INDEXembabel-content-index; CREATE VECTOR INDEX embabel_content_index FOR (c:Chunk) ON (c.embedding) OPTIONS {indexConfig: {vector.dimensions: 384,vector.similarity_function: 'cosine' }}One or the other must be the source of truth - either embabel-hub is correct and the indexes loaded in must change or the loaded indexes are correct and embabel-hub must reference them.