Thanks a lot Shawn for your details reply.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Thanks a lot Shawn for your reply. I'm using SolrCloud v7.3 and using
schema-less approach. I add documents and new fields automatically added in
managed-schema files. I've tried it several times and it stops at around
13,500 fields.
If I try to add fields using SolrCloud API I can add them, but ca
Hi Solr community,
I would like some help with a strange behavior that I observe on the
unified highlighter.
Here is the configuration of my highlighter :
on
unified
false
content_fr content_en exactContent
true
CHARACTER
html
200
51200
I indexed some html document
Thanks, everyone for your replies.
I tried using "-Dtests.badapples=false" flag but it didn't help.
I will try again without *ant test* command.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi all,
A couple of years ago I ran two free Lucene Hackdays in London and
Boston (the latter just before Lucene Revolution). Here's what we got up
to with the kind support of Alfresco, Bloomberg, BA Insight and
Lucidworks
http://www.flax.co.uk/blog/2016/10/21/tale-two-cities-two-lucene-hackd
Charlie,
I might be able to get sponsorship from SearchStax for eve/drinks in
Montreal. Do you want to start a thread offline?
Sameer.
On Thu, Jul 12, 2018 at 4:28 AM Charlie Hull wrote:
> Hi all,
>
> A couple of years ago I ran two free Lucene Hackdays in London and
> Boston (the latter just
Hello everybody,
I work on a SOLR version 6.0.0. I use the JSON request API to facet the
results. Here is a SOLR query example :
{"query":"object_type_s:contact","params":{"wt":"json","start":0,"rows":10},"filter":[],"facet":"byNestedGammes":{"type":"terms","field":"gamme","domain":{"blockChildre
Hi folks,
I am trying to track down what might have changed and where i could tweak a
configuration that worked under Solr 6.5.1 but which is not working as
expected under 7.3.1 or 7.4.0. We have default "qf" and "pf" defeined for
our select handler, along with "special" versions of those for use
This may be the issue:
https://issues.apache.org/jira/browse/SOLR-11501
If it turns out that this causing the problem, please create a jira. It's
important to discuss how SOLR-11501 is affecting real deployments.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Jul 12, 2018 at 12:30 PM, Ada
HI,
i have a date field which needs to copied to different field with different
format/value. is there any way to achieve this using copy field ? or needs
to be done when creating solr document itself.
lets say createdDate is 10-23-2017 10:15:00, it needs to be copied to
transformedDate field as
Hi Anil,
The copy Field directive is not what you're looking for because it doesn't
change the stored value of a field.
What you need is an Update Request Processor, which is a kind of
interceptor in the indexing chain (i.e. It allows you to change an incoming
document before it gets indexed).
Unf
This seems like an XY problem, you've asked how to do X without
explaining _why_ (the Y).
If this is just because you want to search the field without having
to specify the full string, consider a DateRangeField.
Best,
Erick
On Thu, Jul 12, 2018 at 10:22 AM, Anil wrote:
> HI,
>
> i have a date
Thanks Joel, that's it!
I had tried all sorts of variants on the search terms but somehow missed
that issue (probably because my eyes glazed over before getting to the 7.2
upgrade notes). While we were negatively impacted by the change, given
the existence of a simple workaround (anybody coming
XY question not withstanding, this is exactly the sort of thing one might
want to do in their indexing pipeline. For example:
https://github.com/nsoft/jesterj/blob/master/code/ingest/src/main/java/org/jesterj/ingest/processors/SimpleDateTimeReformatter.java
On Thu, Jul 12, 2018 at 1:34 PM, Erick
Hi - I'm using SolrCloud 7.3.1 and calling a search from Java using:
org.apache.solr.client.solrj.response.QueryResponse response =
CloudSolrClient.query(ModifiableSolrParams)
If the ModifiableSolrParams are long, I get an error:
Bad Message 414reason: URI Too Long
I have the maximum number o
Have you tried using POST, instead of GET:
https://lucene.apache.org/solr/7_3_0//solr-solrj/org/apache/solr/client/solrj/SolrClient.html#query-java.lang.String-org.apache.solr.common.params.SolrParams-org.apache.solr.client.solrj.SolrRequest.METHOD-
Also, if you have a set of parameters that do no
Gus,
Perhaps you might try the technique described in the forwarded exchange
below. It has been working very nicely for me.
Terry
Forwarded Message
Subject:Re: Changing Field Assignments
Date: Tue, 12 Jun 2018 12:21:16 +0900
From: Yasufumi Mizo
On 7/12/2018 12:48 PM, Joe Obernberger wrote:
> Hi - I'm using SolrCloud 7.3.1 and calling a search from Java using:
>
> org.apache.solr.client.solrj.response.QueryResponse response =
> CloudSolrClient.query(ModifiableSolrParams)
>
> If the ModifiableSolrParams are long, I get an error:
> Bad Messa
Hi Erick,
Thank you for your suggestions.
Regards,
Sharif
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
HI Eric,
i have a schema with a date field (tweetedDate) with 10-23-2017 10:15:00
format. Same schema is used with number of collections. i have to index the
date field with different formats in different collections.
lets says collections as collection-day, collection-hour, etc
if the date fie
Thanks Andrea. i will write update processor in index pipe line.
I feel this is very good feature to support.
Thanks,
Anil
On 12 July 2018 at 22:59, Andrea Gazzarini wrote:
> Hi Anil,
> The copy Field directive is not what you're looking for because it doesn't
> change the stored value of a fi
Hi All,
I have index which is being lying in production for quite some time. Now we
need to delete the documents based on Date range, i.e., after 270 days we
should be able to delete the old documents. beyond that many days old. I
hear about this feature Time to Live i need to know couple of thin
Hi All,
I have index which is being lying in production for quite some time. Now we
need to delete the documents based on Date range, i.e., after 270 days we
should be able to delete the old documents. beyond that many days old. I
hear about this feature Time to Live i need to know couple of thin
23 matches
Mail list logo