We found out that when we use colons ":" in our search, that it seems to
break? We searched for a time, like "09:22:50" and the request kept
pending. Is this a common issue, or did we do something wrong?
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.
We found out that when we use colons ":" in our search, that it seems
to break? We searched for a time, like "09:22:50" and the request kept
pending. Is this a common issue, or did we do something wrong?
Disclaimer: The information contained in this message and attachments
is intended solely for the attention and use of the named addressee
and may be confidential. If you are not the intended recipient, you
are reminded that the information remains the property of the sender.
You must not use, disclose, distribute, copy, print or rely on this
e-mail. If you have received this message in error, please contact the
sender immediately and irrevocably delete this message and any copies.
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.
We found out that when we use colons ":" in our search, that it seems
to break? We searched for a time, like "09:22:50" and the request kept
pending. Is this a common issue, or did we do something wrong?
Disclaimer: The information contained in this message and attachments
is intended solely for the attention and use of the named addressee
and may be confidential. If you are not the intended recipient, you
are reminded that the information remains the property of the sender.
You must not use, disclose, distribute, copy, print or rely on this
e-mail. If you have received this message in error, please contact the
sender immediately and irrevocably delete this message and any copies.
I don't think such a complex thing is necessary, just these 3 seps:
All I was asking for was a recreation, which you have provided below
However, for anything more complex, I'd want to be able to copy and
paste it in order to test it out.
so your search string is being parsed according to the syntax described
above. Colons are used to introduce field names. But FOO:FOO:FOO is a
syntax error, so you should have received an error in response from ES.
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.
I don't think such a complex thing is necessary, just these 3 seps:
All I was asking for was a recreation, which you have provided below
However, for anything more complex, I'd want to be able to copy and
paste it in order to test it out.
so your search string is being parsed according to the syntax described
above. Colons are used to introduce field names. But FOO:FOO:FOO is a
syntax error, so you should have received an error in response from ES.
Disclaimer: The information contained in this message and attachments
is intended solely for the attention and use of the named addressee
and may be confidential. If you are not the intended recipient, you
are reminded that the information remains the property of the sender.
You must not use, disclose, distribute, copy, print or rely on this
e-mail. If you have received this message in error, please contact the
sender immediately and irrevocably delete this message and any copies.
2012/9/21 Clinton Gormley clint@traveljury.com
Hi Robin
>
>
> I don't think such a complex thing is necessary, just these
3 seps:
All I was asking for was a recreation, which you have provided
below :)
However, for anything more complex, I'd want to be able to
copy and
paste it in order to test it out.
> 1. Create an index
> 2. Insert "[DEBUG] Fri Sep 21 19:38:58 CEST 2012"
> 3. Search for " Fri Sep 21 19:38:58 CEST 2012" (using a
browser on
> localhost: http://localhost:9200/2012-09-21/_search?q=Fri%
20Sep%2021%
> 2019:38:58 )
The ?q= search corresponds to the query string query
http://www.elasticsearch.org/guide/reference/query-dsl/query-string-query.html
which uses the Lucene query parser syntax
http://lucene.apache.org/core/3_6_0/queryparsersyntax.html
so your search string is being parsed according to the syntax
described
above. Colons are used to introduce field names. But
FOO:FOO:FOO is a
syntax error, so you should have received an error in response
from ES.
I get:
ParseException[Cannot parse 'Fri Sep 21 19:38:58': Encountered
" ":" ": ""
clint
--
We will in the future as we're going to write our own interface on ES and
perform many post-processing steps. This was just for some manual testing
which caused me a tiny headache...
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.
Disclaimer: The information contained in this message and attachments
is intended solely for the attention and use of the named addressee
and may be confidential. If you are not the intended recipient, you
are reminded that the information remains the property of the sender.
You must not use, disclose, distribute, copy, print or rely on this
e-mail. If you have received this message in error, please contact the
sender immediately and irrevocably delete this message and any copies.
2012/9/21 Clinton Gormley clint@traveljury.com
Hi Robin
>
>
> I don't think such a complex thing is necessary, just these
3 seps:
All I was asking for was a recreation, which you have provided
below :)
However, for anything more complex, I'd want to be able to
copy and
paste it in order to test it out.
> 1. Create an index
> 2. Insert "[DEBUG] Fri Sep 21 19:38:58 CEST 2012"
> 3. Search for " Fri Sep 21 19:38:58 CEST 2012" (using a
browser on
> localhost: http://localhost:9200/2012-09-21/_search?q=Fri%
20Sep%2021%
> 2019:38:58 )
The ?q= search corresponds to the query string query
which uses the Lucene query parser syntax
http://lucene.apache.org/core/3_6_0/queryparsersyntax.html
so your search string is being parsed according to the syntax
described
above. Colons are used to introduce field names. But
FOO:FOO:FOO is a
syntax error, so you should have received an error in response
from ES.
I get:
ParseException[Cannot parse 'Fri Sep 21 19:38:58': Encountered
" ":" ": ""
clint
--
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
