Hi Alicia,
I do not know it will help but I answer.
The query will search the *"Term"* in the Index.
When developer uses Elasticsearch first time, they confuse Full text
queries with Term level queries much.
These two are very different.
Please check.
Full text queries :
https://www.elastic.co/g
Hi Alica,
You might want to ask your question at the Elasticsearch mailing list (
http://discuss.elastic.co) or at Magento's (https://community.magento.com/).
Because Lucene is really just a library, with an very open-ended way of
doing document scoring that could mix in any number of ways of doin
Thank you all for the feedback and your point of views.
Peyman
On Nov 18, 2011, at 2:47 AM, Peter Karich wrote:
> Hi Lukáš, hi Mark
>
>> https://issues.apache.org/jira/browse/SOLR-839
>
>
> thanks for pointing me there
>
>
>>> although some parameters are available as URL parameters as w
Hi Lukáš, hi Mark
> https://issues.apache.org/jira/browse/SOLR-839
thanks for pointing me there
> > although some parameters are available as URL parameters as well in ES
> Not sure if I understood exactly what you meant here but do you know you
> can always use "source" URL parameter to p
Hi Peter,
On Fri, Nov 18, 2011 at 12:11 AM, Peter Karich wrote:
>
>
> > I don't think it's possible.
>
> Eh, of course its possible (if I would understand it I would do it. no,
> no, just joking ;))
>
> and yes, Solr its a shorter for some common use cases. I don't think
> that there is a 'best'
The XML query parser can map to Lucene one to one as well - hasn't seemed
to pick up enough steam to be included with Solr yet, but there has been
some commotion so it's likely to go in at some point. Not enough demand yet
I guess. https://issues.apache.org/jira/browse/SOLR-839 XML Query Parser
Sup
> I don't think it's possible.
Eh, of course its possible (if I would understand it I would do it. no,
no, just joking ;))
and yes, Solr its a shorter for some common use cases. I don't think
that there is a 'best', but JSON can map 1:1 to lucene.
The biggest problem with ES's syntax is that
: > Maybe someone can post the equivalent query in ElasticSearch?
:
: I don't think it's possible. Hoss threw in the kitchen sink into his
: "contrived' example.
exactly ... i have no idea if that type of query is possible with ES, but
it was not intended to be an example of a "typical" Solr q
>
> Other parameters such as filters, faceting, highlighting, sorting,
> etc, don't normally have any hierarchy.
I regularly mix filters and queries inside Boolean logic. Attempts to structure
data (e.g. geocoding) don't always achieve 100% coverage and so for better
recall you must also resor
On Thu, Nov 17, 2011 at 3:44 PM, Michael McCandless
wrote:
> Maybe someone can post the equivalent query in ElasticSearch?
I don't think it's possible. Hoss threw in the kitchen sink into his
"contrived' example.
Here's a super simple example:
JSON:
{
"sort" : [
{ "age" : {"order"
On Thu, Nov 17, 2011 at 3:40 PM, Mark Harwood wrote:
> JSON or XML can reflect more closely the hierarchy in the underlying Lucene
> query objects.
We normally use the Lucene QueryParser syntax itself for that (not
HTTP parameters).
Other parameters such as filters, faceting, highlighting, sort
Maybe someone can post the equivalent query in ElasticSearch? Then at
least we have a fair comparison of the two syntaxes, for this one
(complex) query at least...
Mike McCandless
http://blog.mikemccandless.com
On Thu, Nov 17, 2011 at 3:21 PM, Yonik Seeley
wrote:
> On Thu, Nov 17, 2011 at 3:18
I don't think of queries as inherently flat in the way HTTP request parameters
are with their name=value pairings.
JSON or XML can reflect more closely the hierarchy in the underlying Lucene
query objects.
For me using a "flat" query interface feels a bit like when you start off
trying to manag
On Thu, Nov 17, 2011 at 3:18 PM, Uwe Schindler wrote:
> Sorry, this query is really ununderstandable. Those complex queries should
> have a meaningful language, e.g. a JSON object structure
There are upsides and downsides to that. A big JSON object graph
would be easier to *read* but certainly n
> Or if you're just unjustifiably bitching about Solr again
Sorry, this query is really ununderstandable. Those complex queries should
have a meaningful language, e.g. a JSON object structure (like
XMLQueryParser, but instead JSON). Those queries are never entered by users
only by machines, why no
On Thu, Nov 17, 2011 at 8:03 PM, Yonik Seeley
wrote:
> On Thu, Nov 17, 2011 at 2:53 PM, Simon Willnauer
> wrote:
>> dude, look at this query... its insane isn't it :)
>
> Sorry... what's the equivalent you'd like instead?
oh, I think there are many ways to design a DSL for querying..
something I
On Nov 17, 2011, at 9:03 PM, Yonik Seeley wrote:
>> dude, look at this query... its insane isn't it :)
>
> Sorry... what's the equivalent you'd like instead?
> Or if you're just unjustifiably bitching about Solr again, maybe I
> should take a stroll through Lucene land and bitch about
> incompre
On Thu, Nov 17, 2011 at 2:53 PM, Simon Willnauer
wrote:
> dude, look at this query... its insane isn't it :)
Sorry... what's the equivalent you'd like instead?
Or if you're just unjustifiably bitching about Solr again, maybe I
should take a stroll through Lucene land and bitch about
incomprehensi
On Thu, Nov 17, 2011 at 9:25 AM, Peter Karich wrote:
>
>>> : "Think of the Query DSL as an AST of queries"
>>> : http://www.elasticsearch.org/guide/reference/query-dsl/
>>>
>>> I'm not familiar with ES, but FWIW: based on that one page the "Query DSL"
>>> doesn't really sound much more powerful th
>> : "Think of the Query DSL as an AST of queries"
>> : http://www.elasticsearch.org/guide/reference/query-dsl/
>>
>> I'm not familiar with ES, but FWIW: based on that one page the "Query DSL"
>> doesn't really sound much more powerful then what you can do with nested
>> queries, local params, and
On Wed, Nov 16, 2011 at 10:18 PM, Chris Hostetter
wrote:
>
> : "Think of the Query DSL as an AST of queries"
> : http://www.elasticsearch.org/guide/reference/query-dsl/
>
> I'm not familiar with ES, but FWIW: based on that one page the "Query DSL"
> doesn't really sound much more powerful then wha
: "Think of the Query DSL as an AST of queries"
: http://www.elasticsearch.org/guide/reference/query-dsl/
I'm not familiar with ES, but FWIW: based on that one page the "Query DSL"
doesn't really sound much more powerful then what you can do with nested
queries, local params, and param refs usin
The docs are slim on examples.
On Wed, Nov 16, 2011 at 3:35 PM, Peter Karich wrote:
>
>>> even high complexity as ES supports lucene-like query nesting via JSON
>> That sounds interesting. Where is it described in the ES docs? Thanks.
>
> "Think of the Query DSL as an AST of queries"
> http://w
>> even high complexity as ES supports lucene-like query nesting via JSON
> That sounds interesting. Where is it described in the ES docs? Thanks.
"Think of the Query DSL as an AST of queries"
http://www.elasticsearch.org/guide/reference/query-dsl/
For further info ask on ES mailing list.
Reg
> even high complexity as ES supports lucene-like query nesting via JSON
That sounds interesting. Where is it described in the ES docs? Thanks.
On Wed, Nov 16, 2011 at 1:36 PM, Peter Karich wrote:
> Hi,
>
> its not really fair to compare NRT of Solr to ElasticSearch.
> ElasticSearch provides
Hi,
its not really fair to compare NRT of Solr to ElasticSearch.
ElasticSearch provides NRT for distributed indices as well... also when
doing heavy indexing Solr lacks real NRT.
The only main disadvantages of ElasticSearch are:
* only one (main) committer
* no autowarming
> the ES team in t
On Wed, Nov 16, 2011 at 10:36 AM, Shashi Kant wrote:
> I had posted this earlier on this list, hope this provides some answers
>
> http://engineering.socialcast.com/2011/05/realtime-search-solr-vs-elasticsearch/
Except it's an out of date comparison.
We have NRT (near real time search) in Solr no
I had posted this earlier on this list, hope this provides some answers
http://engineering.socialcast.com/2011/05/realtime-search-solr-vs-elasticsearch/
On Wed, Nov 16, 2011 at 9:53 AM, Federico Fissore wrote:
> Peyman Faratin, il 16/11/2011 15:12, ha scritto:
>
> Hi
>>
>> A client is conside
Peyman Faratin, il 16/11/2011 15:12, ha scritto:
Hi
A client is considering moving from Lucene to ElasticSearch. What is the
community's opinion on ES?
thank you
we have recently compared ES to Solr to estimate the effort of evolving
our search infrastructure (it was game like: two teams t
Under the covers, ElasticSearch contains mutliple lucene indexes -- so the
full expressiveness of lucene queries are translatable to ElasticSearch --
but the benefit of using ES as an abstraction layer to give sharded
searches is something attractive enough that we're looking at it too. ;)
We typ
30 matches
Mail list logo
