Creating indexes on embedded maps/objects fails
See original GitHub issueclass Customer { address: { address…, city…, postalCode… } }
create index CustomerAddress on Customer(address.address) NOTUNIQUE (or FULLTEXT etc.)
responds with :
com.orientechnologies.orient.core.index.OIndexException: Index with name : 'CustomerAddress' cannot be created on class : 'Customer' because field: 'address.address' is absent in class definition.
After discussion with Luca, it appears that this might just be the property check that is failing even though the indexing could work.
I will be pushing a test case soon. Thanks!
Issue Analytics
- State:
- Created 9 years ago
- Comments:28 (16 by maintainers)
Top Results From Across the Web
can you create indexes on embedded objects in dynamodb
Is there a way that I can create an index on Profile so that I can query for all profiles where Profile.Followers includes...
Read more >Indexing of Embedded Documents - Google Groups
Hello, I have a question about how mongodb indexes embedded documents. Say I would like to index the product embedded doc, what fields...
Read more >Building unique index on array of embedded documents
Hello all, I'm facing some difficulties to create a unique index: Example collection with documents: {"_id":1,“name”:service1 ...
Read more >comparing and ordering integers games
Decimalus Rex Reading, Ordering, and Adding Decimals Decimal Math Game for Kids ... size-1 to objects, and a rank function that maps objects...
Read more >[ABANDONED] Indexing fails sometimes - SEGGER - Forum
Hi I am using the NRF Connect version of SES. I am using it primarily on a Linux VM. I have an issue...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @dcardin
Thank you very much for your feedback, this feature is definitely important for us as well and we tried to add it to the roadmap more than once. Unfortunately, as you said, it’s not there yet, but given the attention it has (and thanks to your comments and all the feedback on this issue) I’ll try to raise it to the attention of the team again and see if we can speed up this development
Thanks
Luigi
@schernolyas What he meant was that he thought this bug was finally addressed by the team and he was super happy about it. Then he realized that it’s still not fixed so he had a big up and down because of it. I raised this issue 4 years ago, and it is THE reason why I am not using Orient on my projects. I really thought it was the best product for document management, but not being to index sub-documents is seriously nuts.
Help us spread the love, guys @lvca @laa @luigidellaquila