Illegal chars in doc id


(g) #1

am looking to create (index) a documents with base-64 chars that include slashes.
ES reliably returns http. 400 :slight_smile:

What is the preferred work-around when this is the case? In this context, am using this as Doc ID and will not be searching on it; rather just as a nosql key lookup.

thanks in advance!

-gleeco


(Shay Banon) #2

How are you indexing it? Escaping it should work.

On Fri, Aug 19, 2011 at 3:10 AM, gleeco gleeco@gmail.com wrote:

am looking to create (index) a documents with base-64 chars that include
slashes.
ES reliably returns http. 400 :slight_smile:

What is the preferred work-around when this is the case? In this context,
am
using this as Doc ID and will not be searching on it; rather just as a
nosql
key lookup.

thanks in advance!

-gleeco

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/illegal-chars-in-doc-id-tp3266673p3266673.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.


(g) #3

indeed- just wanted to get verification that adding a key should use URI escaping.
Everything works fine w/ escaping: docids --and doctype too.
And for index names, the error message is self-evident:

{"error": ".. must not contain the following characters [\, /, *, ?, ", <, >, |, , ,]]","status":400}

thanks!


(system) #4