Tried with plong, pint and string. Reindexed after each change. The sort
results on numeric values being shown are the same -
Ascending
1
10
100
2
2100
3
Descending
999
99
9
88
88
On Fri, 6 Dec 2019 at 17:15, Anuj Bhargava wrote:
> Numeric sorting. Did the re-indexing. But did
Please look at the admin UI>>collection_or_core>>analysis page. That will tell
you exactly how your input is being transformed. Very often
WordDelimiter(Graph)FilterFactory is what breaks data up like this, that’s what
it’s _designed_ for.
Best,
Erick
> On Dec 6, 2019, at 11:25 AM, rhys J wro
On Fri, Dec 6, 2019 at 11:21 AM David Hastings wrote:
> whats the field type for:
> clt_ref_no
>
It is a text_general field because it can have numbers or alphanumeric
characters.
*_no isnt a default dynamic character, and owl-2924-8 usually translates
> into
> owl 2924 8
>
>
So it's matching o
whats the field type for:
clt_ref_no
*_no isnt a default dynamic character, and owl-2924-8 usually translates into
owl 2924 8
David J. Hastings | Lead Developer
dhasti...@wshein.com | 716.882.2600 x 176
William S. Hein & Co., Inc.
2350 North Forest Road | Getzville, NY 14068
www.wshein.com/con
You can enable debug which will show you what matches and why. Check
the reference guide for parameters:
https://lucene.apache.org/solr/guide/8_1/common-query-parameters.html#debug-parameter
Regards,
Alex.
On Fri, 6 Dec 2019 at 11:00, rhys J wrote:
>
> I have a search box that is just searchi
I have a search box that is just searching every possible core, and every
possible field.
When I enter 'owl-2924-8', I expect the clt_ref_no of OWL-2924-8 to float
to the top, however it is the third result in my list.
Here is the code from the search:
on_data({
"responseHeader":{
"status"
Thanks you guys, this has been educational, i uploaded up to now, the
server was restarted after adding the extra memory, so
https://gceasy.io/my-gc-report.jsp?p=c2hhcmVkLzIwMTkvMTIvNi8tLXNvbHJfZ2MubG9nLjAuY3VycmVudC0tMTQtMjEtMTA=&channel=WEB
is what im looking at. tuning the JVM is new to me, so
Hey Erick,
We have just upgraded to 8.3 before starting the indexing. We were on 6.6
before that.
Thank you for your continued support and resources. Again, I have already
taken your suggestion to start afresh and that's what I'm going to do.
Don't get me wrong but I have been just asking doubts.
Nothing implicitly handles optimization, you must continue to do that
externally.
Until you get to the bottom of your indexing slowdown, I wouldn’t bother
with it at all, trying to do all these things at once is what lead to your
problem in the first place, please change one thing at a time. You s
Because you use individual collections, you really don’t have to care
about getting it all right up front.
Each collection can be created on a specified set of nodes, see the
“createNodeSet”
parameter of the collections API “CREATE” command.
And let’s say you figure out later that you need mor
A replication shouldn’t have consumed that much heap. It’s mostly I/O, just a
write through. If replication really consumes huge amounts of heap we need to
look at that more closely. Personally I suspect/hope it’s coincidental, but
that’s only a guess. You can attach jconsole to the running proc
Actually at about that time the replication finished and added about 20-30gb to
the index from the master. My current set up goes
Indexing master -> indexer slave/production master (only replicated on
command)-> three search slaves (replicate each 15 minutes)
We added about 2.3m docs, then I re
Numeric sorting. Did the re-indexing. But didn't work.
Regards,
Anuj
On Fri, 6 Dec 2019 at 16:44, Munendra S N wrote:
> >
> > What should I use for numeric search.
>
> numeric search or numeric sorting?
>
> I tried with pint also, but the result was the same.
>
> It should have worked. please
Tokenizer is required
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 4:14 PM Bernd Fehling
wrote:
> Hi Munendra S N,
>
> thanks for the hint about Tokenizer.
> Could I omit Tokenizer at all or is it needed by LowerCaseFilterFactory?
>
> The field "firstname" has no facetting and sorting.
> Also
>
> What should I use for numeric search.
numeric search or numeric sorting?
I tried with pint also, but the result was the same.
It should have worked. please make sure data is reindexed after fieldType
changes
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 4:10 PM Anuj Bhargava wrote:
> I
Hi Munendra S N,
thanks for the hint about Tokenizer.
Could I omit Tokenizer at all or is it needed by LowerCaseFilterFactory?
The field "firstname" has no facetting and sorting.
Also, I want to keep the raw content as is, with capital letters and so on.
I think update processors and preprocessin
I tried with pint also, but the result was the same. What should I use for
numeric search.
Regards,
Anuj
On Fri, 6 Dec 2019 at 15:55, Munendra S N wrote:
> Hi Anuj,
> As the field type is String, lexicographical sorting is done, not numeric
> sorting.
>
> Regards,
> Munendra S N
>
>
>
> On Fri
Instead of StandardTokenizerFactory use KeywordTokenizerFactory which emits
whole text as a single token. Once you make this change, full reindexing
needs to be done. After field type, some functionality might not be
performant on the field like faceting, sorting.
I'm not sure if there are any out-
Hi Anuj,
As the field type is String, lexicographical sorting is done, not numeric
sorting.
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 3:12 PM Anuj Bhargava wrote:
> When I sort desc on posting_id sort=posting_id%20desc, I get the following
> result
> "posting_id":"313"
> "posting_id":"
Dear list,
for one field I want to change fieldType from string to something
equal to string, but only lowercase.
currently:
new:
Is this the right replacement for "string"?
Are the attributes for solr.TextField ok?
Regards
Bernd
Hi Shawn,
Thanks for your response!
Yes! 500 collections.
Each collection/core has around 50k to 50L documents/jsons (depending upon
the client). We made one core for each client. Each json has 15 fields.
It already in production as as Solr stand alone server.
We want to use SolrCloud for it now,
Yes! 500 collections.
Each collection/core has around 50k to 50L documents/jsons (depending upon
the client). We made one core for each client. Each json has 15 fields.
It already in production as as Solr stand alone server.
We want to use SolrCloud for it now, so as to make it scalable for future
22 matches
Mail list logo
