CosmoBean
JJanusGraph
•Created by CosmoBean on 4/1/2024 in #questions
Issues faced for consistent indexing (both Composite & Mixed) [ElasticSearch]
--> Schema was provisioned, and then, all the schema was verified and the management objects closed. [All the indexes were in enabled state, both mixed and composite]
--> [Issue:1]
Index wasn't created in ElasticSearch, giving a 404, when a vertex totals direct Index Query is performed
--> As a work around. for initial data 1000 Documents of sample data was ingested, and as we expected, the indexes were not present
--> data was re-indexed. Indexes were created in ElasticSearch, and some composite indexes needed re-Indexing as well. After reindexing, the performance was as expected
--> Closed the graph instances after testing the reindexed data
--> Restarted the ingestion process for the full data. [23k Documents]
--> [Issue:2] Once the Ingestion was done. Opened the graph, The indexes did not get updated.
--> The index-query returned old response as before, not with the updated count [Mixed Index]. The composite Index was working as expected in this case giving the right count
-->[Issue:3] [SOLVED] (edit) Even though a unique index constraint was placed on this Vertex, It did not get enforced and some duplicates were created.
--> Unique Index was placed on both Composite as well as the Mixed Index
The unreliable nature of the indexes wasn't something I was expecting working with Janusgraph. Where I am in need to constantly re-index the data for the indexes to work as expected.
Please help me, and guide me if i got any step wrong. If any additional information needed, please feel free to ask me18 replies