Might worth while mentioning it in Terms documentation that minimum_match
should not be used in filter. I assume 1 value is used
If i try it I get QueryParsingException[[award] [terms] filter does not
support [minimum_match]]
--
Same goes for Bool minimum_number_should_match
On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote:
Might worth while mentioning it in Terms documentation that minimum_match
should not be used in filter. I assume 1 value is usedIf i try it I get QueryParsingException[[award] [terms] filter does not
support [minimum_match]]
--
Yes that is correct. FYI, I have gone though the source code and
documented every possible option for each query, filter, and facet in
Elasticsearch while I was implementing Elastic.js. You can use the
Elastic.js docs even if you are only using the REST api.
http://docs.fullscale.co/elasticjs/
Elastic.js uses the camelCase options, for the REST api you should use
underscore_notation. You can always write Elastic.js and use the
translator (The domain name Fullscale.co is for sale | Dan.com) as well. Note that
Elastic.js includes Lucene 4.0 options that are only available in the
master branch of Elasticsearch.
Thanks,
Matt Weber
On Tue, Jan 22, 2013 at 2:13 PM, AlexR roytmana@gmail.com wrote:
Same goes for Bool minimum_number_should_match
On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote:
Might worth while mentioning it in Terms documentation that minimum_match
should not be used in filter. I assume 1 value is usedIf i try it I get QueryParsingException[[award] [terms] filter does not
support [minimum_match]]--
--
Thanks Matt.
Are your doc hand written with more info than official ES or a organized ES
docs?
Have not had chance to try your API with ExtJS yet - just learning and
prototyping ES via REST for now. Once I a reasonable understanding what and
how I want to do will switch to your API
On Tue, Jan 22, 2013 at 5:48 PM, Matt Weber matt.weber@gmail.com wrote:
Yes that is correct. FYI, I have gone though the source code and
documented every possible option for each query, filter, and facet in
Elasticsearch while I was implementing Elastic.js. You can use the
Elastic.js docs even if you are only using the REST api.The domain name Fullscale.co is for sale | Dan.com
Elastic.js uses the camelCase options, for the REST api you should use
underscore_notation. You can always write Elastic.js and use the
translator (The domain name Fullscale.co is for sale | Dan.com) as well. Note that
Elastic.js includes Lucene 4.0 options that are only available in the
master branch of Elasticsearch.Thanks,
Matt WeberOn Tue, Jan 22, 2013 at 2:13 PM, AlexR roytmana@gmail.com wrote:
Same goes for Bool minimum_number_should_match
On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote:
Might worth while mentioning it in Terms documentation
that minimum_match should not be used in filter. I assume 1 value is usedIf i try it I get QueryParsingException[[award] [terms] filter does not
support [minimum_match]]--
--
--
The Elastic.js documentation covers every possible option for each query,
filter, and facet within Elasticsearch. We used a combination of the
official Elasticsearch docs, lucene docs, and information we have written
to do this.
On Tue, Jan 22, 2013 at 2:53 PM, Alex Roytman roytmana@gmail.com wrote:
Thanks Matt.
Are your doc hand written with more info than official ES or
a organized ES docs?Have not had chance to try your API with ExtJS yet - just learning and
prototyping ES via REST for now. Once I a reasonable understanding what and
how I want to do will switch to your APIOn Tue, Jan 22, 2013 at 5:48 PM, Matt Weber matt.weber@gmail.com wrote:
Yes that is correct. FYI, I have gone though the source code and
documented every possible option for each query, filter, and facet in
Elasticsearch while I was implementing Elastic.js. You can use the
Elastic.js docs even if you are only using the REST api.The domain name Fullscale.co is for sale | Dan.com
Elastic.js uses the camelCase options, for the REST api you should use
underscore_notation. You can always write Elastic.js and use the
translator (The domain name Fullscale.co is for sale | Dan.com) as well. Note that
Elastic.js includes Lucene 4.0 options that are only available in the
master branch of Elasticsearch.Thanks,
Matt WeberOn Tue, Jan 22, 2013 at 2:13 PM, AlexR roytmana@gmail.com wrote:
Same goes for Bool minimum_number_should_match
On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote:
Might worth while mentioning it in Terms documentation
that minimum_match should not be used in filter. I assume 1 value is usedIf i try it I get QueryParsingException[[award] [terms] filter does not
support [minimum_match]]--
--
--
--
cool good job it'll be a great learning resource!
On Tue, Jan 22, 2013 at 6:04 PM, Matt Weber matt.weber@gmail.com wrote:
The Elastic.js documentation covers every possible option for each query,
filter, and facet within Elasticsearch. We used a combination of the
official Elasticsearch docs, lucene docs, and information we have written
to do this.On Tue, Jan 22, 2013 at 2:53 PM, Alex Roytman roytmana@gmail.com wrote:
Thanks Matt.
Are your doc hand written with more info than official ES or
a organized ES docs?Have not had chance to try your API with ExtJS yet - just learning and
prototyping ES via REST for now. Once I a reasonable understanding what and
how I want to do will switch to your APIOn Tue, Jan 22, 2013 at 5:48 PM, Matt Weber matt.weber@gmail.com wrote:
Yes that is correct. FYI, I have gone though the source code and
documented every possible option for each query, filter, and facet in
Elasticsearch while I was implementing Elastic.js. You can use the
Elastic.js docs even if you are only using the REST api.The domain name Fullscale.co is for sale | Dan.com
Elastic.js uses the camelCase options, for the REST api you should use
underscore_notation. You can always write Elastic.js and use the
translator (The domain name Fullscale.co is for sale | Dan.com) as well. Note that
Elastic.js includes Lucene 4.0 options that are only available in the
master branch of Elasticsearch.Thanks,
Matt WeberOn Tue, Jan 22, 2013 at 2:13 PM, AlexR roytmana@gmail.com wrote:
Same goes for Bool minimum_number_should_match
On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote:
Might worth while mentioning it in Terms documentation
that minimum_match should not be used in filter. I assume 1 value is usedIf i try it I get QueryParsingException[[award] [terms] filter does
not support [minimum_match]]--
--
--
--
--