Hi all,
I created a patch for new statistics facet capabilities to StatsComponent facet
- limit, sort and missing.
This can be found here: https://issues.apache.org/jira/browse/SOLR-5972
Can it have committer attention?
Thanks.
for reference implementation to Sanitize Unknown SolrFields, you can see
below link
https://github.com/cloudera/cdk/blob/master/cdk-morphlines/cdk-morphlines-solr-core/src/main/java/com/cloudera/cdk/morphline/solr/SanitizeUnknownSolrFieldsBuilder.java
On Sat, Aug 2, 2014 at 8:24 PM, Umesh Prasa
Hi all,
I have a question regarding field collapsing.
Has anyone successfully used SOLR to roll up more information than just
"numFound" in the response to a group query?
For some background, I'm trying to see if any artifact in the group has been
marked with a certain priority. Ideally I can
Hi Shalin,
Created JIRA https://issues.apache.org/jira/browse/SOLR-6316
Thanks,
Ramana.
On Sat, Aug 2, 2014 at 10:18 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> No, there is no such API. It will be a good improvement though. Mind
> creating a Jira issue?
>
>
> On Sat, Aug 2,
Anyone?
On Fri, Aug 1, 2014 at 12:31 PM, Salman Akram <
salman.ak...@northbaysolutions.net> wrote:
> We are having an issue in Phrase highlighter with Surround Query Parser
> e.g. *"first thing" w/100 "you must" *brings correct results but also
> highlights individual words of the phrase - first
Hi,
I have a field in my solr schema as below.
After updating some docs via SolrInputDocument, I am not able to query
the updated docs with ClusterId field i.e., when I query using ClusterId the
updated docs are not being retrieved. Can you please help here?
Thanks &
Hi,
You are using a customized surround query parser, right?
Did you check/try with the stock one? I recall correctly
usePhrasehighlighter=true was working in the past for surround.
Ahmet
On Monday, August 4, 2014 8:25 AM, Salman Akram
wrote:
Anyone?
On Fri, Aug 1, 2014 at 12:31 PM, Salm
In order for Atomic Updates to work, all your fields must be stored in the
index. In this case, ClusterId is not stored and is therefore lost on an
atomic update.
--
Regards,
Shalin Shekhar Mangar.
On Mon, Aug 4, 2014 at 11:00 AM, M, Arjun (NSN - IN/Bangalore) <
arju...@nsn.com> wrote:
> Hi,
>
Except if I missed it, nobody yet pointed to
http://solr-vs-elasticsearch.com/
which seems to be fairly up-to-date.
As for performance, I would expect that it is very hard to find one of
the two technologies to be generally ahead. Except for plain blunders
that may be lurking in the code, I w
This all depends on how the tokenizers take your URLs apart. To quickly
see what ended up in the index, go to a core in the UI, select Schema
Browser, select the field containing your URLs, click on "Load Term Info".
In your case, for the field holding the URL you could try to switch to a
toke
That resource is rather superficial. I wouldn't make big decision based on it.
As to performance, ElasticSearch stores the full submitted content as
_source field. That allows it some extra tricks (like fake-nested
documents), but also has a storage price. You can disable the _source
field, but th
11 matches
Mail list logo