New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash error when using multi secondary index #5542
Comments
nevermind. works after i removed leftBound: 'open' from options |
Thanks for the bug report @abovemike. |
@abovemike I looked into this with @mlucy and we believe we understand where the bug came from. Unfortunately the fix will require changes to the on-disk format, and is outside the scope if a bug fix release (2.2.6). Instead we will fix it for RethinkDB 2.3, which isn't that far away either. We also noticed that your index function probably is one nesting too deep with respect to the output. The outer |
Fix in review 3535 |
wow thanks for the fast response. you are exactly right, i was confused on the secondary index function. for anyone that gets here through search, the proper way would be more like this:
looking forward to 2.3! keep up the great work danielmewes & mlucy |
Fixed in next by a57b599. Will ship with RethinkDB 2.3.0 |
crash log file:
document example:
secondary index:
query that crashes the server:
r.db('litecoin').table('transaction').between( [ r.minval, r.minval ], [ r.maxval, r.maxval ], { index: 'addressCreate', leftBound: 'open' } )
i'm basically tagging each Transaction based on an array of strings (Address) using the multi secondary index, so i can efficiently search for all transactions that are involved with a specific Address. any ideas on what i am doing wrong?
The text was updated successfully, but these errors were encountered: