Mikhail,
Where do I implement the buffering? I can not do it in then collect()
method. I can not see how I can get access to what I need in the finish()
method.
Thanks,
John
On Tue, Nov 6, 2018 at 12:44 PM Mikhail Khludnev wrote:
> Not really. It expect to work segment by segment. So it can
Hmmm, afraid I'm out of my depth, perhaps some of the Lucene
folks can chime in.
Sorry I can't be more help.
Erick
On Mon, Nov 12, 2018 at 12:27 AM damian.pawski wrote:
>
> Hi
>
> I had to re-create the index as some tokenizers are not longer supported on
> the 7.x version.
> I have a fresh 7.x
In that case, it seems to be a reporting issue, not a fundamental
replication problem. Whew!
So it's worth raising a JIRA, but since you report the indexes are
identical, I'm not sure how
high a priority it would be. If you do raise a JIRA, you should
reference this discussion.
Best,
Erick
On Mon
Hi,
I have an issue for creating a configset with the V2 API using a configset
property.
Indeed if I enter the command :
curl -X POST -H 'Content-type: application/json' -d '{ "create":{"name":
"Test", "baseConfigSet": "myConfigSet","configSetProp.immutable":
"false"}}' http://localhost:8983/api/
Function query looks like the nearest match to your requirement:
https://lucene.apache.org/solr/guide/7_5/function-queries.html#ms-function
You can use it in the field list too.
Regards,
Alex.
On Mon, 12 Nov 2018 at 09:12, Hullegård, Jimi
wrote:
>
> Hi,
>
> Maybe I have been working too littl
Hi,
Maybe I have been working too little with Solr lately, but I'm stuck on a very
simple problem (in my mind), and need some help.
How can I include the result of a date calculation in the field list?
For example, let's say that the documents in my index contains the date field
'deadline'. Wh
Hi,
SolrJ is a client library that helps your application talk to Solr.
It's not a full application that can be run on its own. So the error
message you got is correct. It's not a standalone application. For
more information on using SolrJ, see the documentation here:
https://lucene.apache.org
From what I've gathered and what's been my experience docValues should
be enabled, but if you can't think of anything else, I'd try turning
them off to see if it makes any difference. As far as I can recall
turning them off will increase usage of Solr's own caches and that
caused noticeable slo
Thanks for the suggestion Ere. It looks like they are actually enabled;
in schema file the field is only marked as stored (field name="_id"
type="string" multiValued="false" indexed="true" required="true"
stored="true") but the admin UI shows DocValues as enabled, so I guess
this is by default.
Thanks for your suggestions. I'll check if the filter queries or the
main query tokenizers/filters might have anything to do with this, but
I'm afraid query optimization can only get us so far. Since we will have
to add facets later, the queries will only become heavier, and there has
to be a w
Hi, Erick
I have about 1300 cores in my test environment for 159 colllections
Today I have wrote a script to check all of them.
For 138 out of 1300 cores "generation" and "indexversion" information returned
by mbeans and replicationhandler do not match.
Most of the replicas has more than 1 gap in
Sofiya,
Do you have docValues enabled for the id field? Apparently that can make
a significant difference. I'm failing to find the relevant references
right now, but just something worth checking out.
Regards,
Ere
Sofiya Strochyk kirjoitti 6.11.2018 klo 16.38:
Hi Toke,
sorry for the late r
Hi
I had to re-create the index as some tokenizers are not longer supported on
the 7.x version.
I have a fresh 7.x index.
Thank you
Damian
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi
I had to re-create the index, as some Tokenizers are no longer supported on
7.X, so I have a fresh 7.x index, but still having issues with the
replication.
Thank you
Damian
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
14 matches
Mail list logo
