Skip to content
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.

Sign up for GitHub

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

Jump to bottom

dropIndex() fails with inverted_range error #66

Closed
apkar opened this issue Feb 6, 2019 · 0 comments
Closed

dropIndex() fails with inverted_range error #66

apkar opened this issue Feb 6, 2019 · 0 comments
Assignees
@apkar
Milestone
1.7.0

Comments

@apkar
Copy link
Contributor

apkar commented Feb 6, 2019 

In [2]: db.coll.create_index('A', name='A_index')
Out[2]: 'A_index'

In [3]: db.coll.drop_index('A_index')

From server logs

S -> C: REPLY: documents=[ { ok: 0.0, err: "Range begin key larger than end key", code: 2005 } ], responseFlags=0, cursorID=0, startingFrom=0 (HEADER: messageLength=108, requestID=0, responseTo=114807987, opCode=1)
@apkar apkar added this to the 1.7.0 milestone Feb 6, 2019
apkar added a commit to apkar/fdb-document-layer that referenced this issue Feb 15, 2019
@apkar
Resolves FoundationDB#66: Fix bad usage of StringRef in dropIndexActo…
f5ba440 
…r(), causing

memory corruption.
apkar added a commit to apkar/fdb-document-layer that referenced this issue Feb 15, 2019
@apkar
Resolves FoundationDB#66: Fix bad usage of StringRef in dropIndexActo…
ec5b224 
…r(), causing

memory corruption.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@apkar apkar

Labels
None yet
Projects
None yet
Milestone
1.7.0
Development

No branches or pull requests
1 participant
@apkar