-
Notifications
You must be signed in to change notification settings - Fork 117
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
DocId needs url-encoding for certain operations #247
Comments
Yes, running ES 5.x >:P https://github.com/bitemyapp/bloodhound/tree/master/src/Database we haven't ported to 6.x yet. Tracking Elastic's churn is labor intensive and we don't have a means of abstracting over the commonalities and differences that we're happy with yet. Happily take a patch that fixes this url-encoding issue. |
Good to know. Thanks, will have a look. By the way, BloodHound works with |
I'm not surprised, but I define compatibility as encompassing the entire test suite. Good hunting! |
Thanks. What would be the way to add support for 6.x? Copy the |
@robinp that's probably the most straight-forward way to go about it. @MichaelXavier sound copacetic to you? |
That'd be how I'd do it! |
I tried to reproduce this issue but could not find a combination that allows me to insert/index a document but not read it, both As a side note, I create a
|
Creating a document with
DocId
containing slashes works, but fetching it withgetDocument
/documentExists
doesn't find it. The difference is that creation uses JSON in POST, while the get/exist uses GET and url parameters.So for the GET case, the
DocId
should be encoded.I found #38 which seemed to be similar. I tried running the tests locally, but many of them failed anyway. Is there a special requirement for setting up a test env? (I have ES 6.5 running locally).
The text was updated successfully, but these errors were encountered: