RE: Schema API specifying different analysers for query and index

different analysers for query and index RefGuide gives this for Adding, I would hope the Replace would be similar: curl -X POST -H 'Content-type:application/json' --data-binary '{ "add-field-type":{ "name":"myNewTextField",

Re: Schema API specifying different analysers for query and index

V2 end point. On Tue, 2 Mar 2021 at 15:25, ufuk yılmaz wrote: > > Hello, > > I’m trying to change a field’s query analysers. The following works but it > replaces both index and query type analysers: > > { > "replace-field-type": { > "name&quo

Schema API specifying different analysers for query and index

Hello, I’m trying to change a field’s query analysers. The following works but it replaces both index and query type analysers: { "replace-field-type": { "name": "string_ci", "class": "solr.TextField",

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

ighlighting. > > > Regarding the existing bug, I think there might be an additional issue > > > here because it happens only when id field contains an underscore > (didn't > > > check for other special characters). > > > Currently I have no other choice but to

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

gt; > > > -Original Message- > > From: David Smiley > > Sent: יום ה 18 פברואר 2021 01:03 > > To: solr-user > > Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field > > Loading => Invalid Index > > > > I think the is

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

formance impact. > > -Original Message- > From: David Smiley > Sent: יום ה 18 פברואר 2021 01:03 > To: solr-user > Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field > Loading => Invalid Index > > I think the issue is this existing bug, but

RE: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

but to use enableLazyFieldLoading=false. I hope it wouldn't have a significant performance impact. -Original Message- From: David Smiley Sent: יום ה 18 פברואר 2021 01:03 To: solr-user Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

Re: Meaning of "Index" flag under properties and schema

ble > >> Properties YesYes Yes Yes > >> Schema YesYesYes Yes > >> Index YesYesYes NO > >> Problematic collection has a Index row under Schema row. No othe

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

the parent e.g. {id:"abc_1", categories_i:{add:1}} >> >> Important: it happens only when "id" contains underscore characters! If >> you'll use "abc-1" it would work. >> >> Thanks in advance, >> Ronen. >> >> -Original M

Re: Meaning of "Index" flag under properties and schema

I didn’t realise that, sorry. The table is like: >> Flags Indexed Tokenized Stored UnInvertible >> Properties YesYesYes Yes >> Schema Yes YesYes Yes >> Index YesYes

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

it happens only when "id" contains underscore characters! If > you'll use "abc-1" it would work. > > Thanks in advance, > Ronen. > > -Original Message- > From: David Smiley > Sent: יום א 14 פברואר 2021 19:17 > To: solr-user > Subject: Re: Atom

RE: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

From: David Smiley Sent: יום א 14 פברואר 2021 19:17 To: solr-user Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index Hello Ronen, Can you please file a JIRA issue? Some quick searches did not turn anything up. It would be super helpful to me if you c

Re: Meaning of "Index" flag under properties and schema

On 2/16/2021 9:16 AM, ufuk yılmaz wrote: I didn’t realise that, sorry. The table is like: Flags Indexed Tokenized Stored UnInvertible Properties YesYesYes Yes Schema YesYesYes Yes Index Yes

RE: Meaning of "Index" flag under properties and schema

I didn’t realise that, sorry. The table is like: Flags Indexed Tokenized Stored UnInvertible Properties YesYesYes Yes Schema YesYesYes Yes Index YesYesYes NO

Re: Meaning of "Index" flag under properties and schema

iling that). When I inspected it, there’s only one difference between it and other dozens of fine working collections, which is, A text_general field in all other collections has the above configuration without my artsy paint edits, but only that problematic collection has an “index” flag

Meaning of "Index" flag under properties and schema

other collections has the above configuration without my artsy paint edits, but only that problematic collection has an “index” flag with indexed tokenized and stored checked. I never saw this “Index” flag before. What does it mean? Sent from Mail for Windows 10

Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

Hello Ronen, Can you please file a JIRA issue? Some quick searches did not turn anything up. It would be super helpful to me if you could list a series of steps with Solr out-of-the-box in 8.8 including what data to index and query. Solr already includes the "tech products" sample d

Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

Hi All, I discovered a strange behaviour with this combination. Not only the atomic update fails, the child documents are not properly indexed, and you can't use highlights on their text fields. Currently there is no workaround other than reindex. Checked on 8.3.0, 8.6.1 and 8.8.0. 1. Configure n

Index rich document and view

Hi, I have all kind of rich documents, such as excel, ppt, PDF, word, jpg ..., I knew Tika or ocr can convert them to text and index it. But when I open the document, the format is changed, how can I keep original document format, is it possible in solr? If not, can I use external field type

Index analyzer concatenate tokens

Hello, I'm trying to index the following token with payload "winter tires|1.4" as an exact match but also I want to apply hunspell lemmer to this token and keep both the original and the lemma. So after all that I want to have the following tokens: "winter tires" with

how to use a compass lucene generated index with solr

With (the latest) lucene 8.7 is it possible to open very old .cfs compound index file of lucene 2.2 with "Luke" ? or alternatively could it be possibile to generate the .idx file for Luke from the .cfs ? the .cfs was generated by compass on top of lucene 2.2, not by lucene dire

Re: Possible bug on LTR when using solr 8.6.3 - index out of bounds DisiPriorityQueue.add(DisiPriorityQueue.java:102)

ithub.com/apache/lucene-solr/blob/branch_8_6/lucene/core/src/java/org/apache/lucene/search/MinShouldMatchSumScorer.java#L107 as the error changes as we change the mm for the second feature: 1 feature with mm=1 and one with mm=3 -> Index 4 out of bounds for length 4 1 feature with mm=1 and one w

Re:Possible bug on LTR when using solr 8.6.3 - index out of bounds DisiPriorityQueue.add(DisiPriorityQueue.java:102)

.java#L520-L525 From: solr-user@lucene.apache.org At: 01/04/21 17:31:44To: solr-user@lucene.apache.org Subject: Possible bug on LTR when using solr 8.6.3 - index out of bounds DisiPriorityQueue.add(DisiPriorityQueue.java:102) Hello, We are trying to update Solr from 8.3.1 to 8.6.3. On Solr 8.

Possible bug on LTR when using solr 8.6.3 - index out of bounds DisiPriorityQueue.add(DisiPriorityQueue.java:102)

e receive that following error message: "metadata":[ "error-class","org.apache.solr.common.SolrException", "root-error-class","java.lang.ArrayIndexOutOfBoundsException"], "msg":"java.lang.ArrayIndexOutOfBoundsExcept

How can i poll Solrcloud via API to get the sum of index size of all shards and replicas?

Hello! We have a Solrcloud(7.4) consisting of 90+ hosts(each of them running multiple nodes of solr, e.g. ports 8983, 8984, 8985), numerous shards(each having several replicas) and numerous collections. I was given a task to summarize the total index size(on disks) of a certain collection. First

Re: Solr8.7 - How to optmize my index ?

will rewrite that, expungeDeletes will not. It’s an open question whether there’s any practical difference, ‘cause if all the segments in your index have > 10% deleted documents, they all get rewritten in either case…. And the mechanism for optimize changed pretty significantly in Solr 7.5,

Re: Solr8.7 - How to optmize my index ?

dexed every month, as the fields in the documents change every month, while documents are added to it daily as well. So when I can go from a 650gb index to a 450gb once in a while it makes a difference if I only have 500gb of memory to work with on the searchers and can fit all the segments straig

RE: Solr8.7 - How to optmize my index ?

Hi Erick, Hi Walter, Thanks for these information, I will learn seriously about the solr article you gave me. I thought it was important to always delete and optimize collection. More information concerning my collection, Index size is about 390Go for 130M docs (3-5ko / doc), around 25 fields

Re: Solr8.7 - How to optmize my index ?

expungeDeletes is unnecessary, optimize is a superset of expungeDeletes. The key difference is commit=true. I suspect if you’d waited until your indexing process added another doc and committed, you’d have seen the index size drop. Just to check, you send the command to my_core but talk about

Re: Solr8.7 - How to optmize my index ?

> > > De : Matheo Software [mailto:i...@matheo-software.com] > Envoyé : mardi 1 décembre 2020 13:28 > À : solr-user@lucene.apache.org > Objet : Solr8.7 - How to optmize my index ? > > > > Hi All, > > > > With Solr5.4, I used the UI button but in

RE: Solr8.7 - How to optmize my index ?

: mardi 1 décembre 2020 13:28 À : solr-user@lucene.apache.org Objet : Solr8.7 - How to optmize my index ? Hi All, With Solr5.4, I used the UI button but in Solr8.7 UI this button is missing. So I decide to use the command line: curl http://xxx:8983/solr/my_core/update?optimize=

Solr8.7 - How to optmize my index ?

Hi All, With Solr5.4, I used the UI button but in Solr8.7 UI this button is missing. So I decide to use the command line: curl http://xxx:8983/solr/my_core/update?optimize=true My collection my_core exists of course. The answer of the command line is: { "responseHeader":{

Re: Can solr index replacement character

be stored. > I mean, honestly, I don't want that irrelevant data stored in my index but > I wondered if solr can index replacement character (U+FFFD �) as string, if > so, how to search it? > And in general, is there any built-in char filtration?! > > Thanks

Can solr index replacement character

Hi community, During integration tests with new data source I have noticed weird scenario where replacement character can't be searched, though, seems to be stored. I mean, honestly, I don't want that irrelevant data stored in my index but I wondered if solr can index replacement charact

Index size issue. Migration from Solr-6.5.1 To Solr-8.6.3

Hi, I am in a process of migrating from Solr-6.5.1 To Solr-8.6.3. The current index size after optimisation is 2.4 TB. We use a 7TB disk for indexing as the optimization needs extra space. Now with the newer Solr the un-optimised index itself got created of size 5+TB which after optimisation

Re: Frequent Index Replication Failure in solr.

looks like youre repeater is grabbing a file that the master merged into a different file, why not lower how often you go from master->repeater, and/or dont commit so often so you can make the index faster On Fri, Nov 13, 2020 at 12:13 PM Parshant Kumar wrote: > All,please help on this

Re: Frequent Index Replication Failure in solr.

All,please help on this On Tue, Nov 3, 2020, 6:01 PM Parshant Kumar wrote: > Hi team, > > We are having solr architecture as *master->repeater-> 3 slave servers.* > > We are doing incremental indexing on the master server(every 20 min) . > Replication of index is done

Partial updates on collection with router.field lead to duplicated index

test_s":{"set":"2"} }] -- /update?*_route_=1* [{ "id":"1", "routerField_s":"1", "test_s":{"set":"3"} }] When I query the collection for document with id:1 and limit = 10 all seems to be fine. However

Frequent Index Replication Failure in solr.

Hi team, We are having solr architecture as *master->repeater-> 3 slave servers.* We are doing incremental indexing on the master server(every 20 min) . Replication of index is done from master to repeater server(every 10 mins) and from repeater to 3 slave servers (every 3 hours). *We are

Re: Index Replication Failure

.java:1443) > at > org.apache.solr.handler.IndexFetcher$FileFetcher.fetch(IndexFetcher.java:1409) > > 2) > WARN : Error getting file length for [segments_568] > java.nio.file.NoSuchFileException: > /data/solr/search/application/core-conf/im-search/data/index.202007110

Re: Index Replication Failure

n/core-conf/im-search/data/index.20200711012319226/segments_568 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:1

Re: Index Replication Failure

None of your images made it through the mail server. You’ll have to put them somewhere and provide a link. > On Oct 17, 2020, at 5:17 AM, Parshant Kumar > wrote: > > Architecture image: If not visible in previous mail > > > > > On Sat, Oct 17, 2020 at 2:38 PM Parshant Kumar > wrote: > Hi

Re: Index Replication Failure

Architecture image: If not visible in previous mail [image: image.png] On Sat, Oct 17, 2020 at 2:38 PM Parshant Kumar wrote: > Hi all, > > We are having solr architecture as below. > > > > *We are facing the frequent replication failure between master to repeater > server as well as between r

Index Replication Failure

Hi all, We are having solr architecture as below. *We are facing the frequent replication failure between master to repeater server as well as between repeater to slave servers.* On checking logs found every time one of the below exceptions occurred whenever the replication have failed. 1)

Re: Index Deeply Nested documents and retrieve a full nested document in solr

ne please help to index the below sample json document into Solr. > > I have following queries on indexing multi level child document. > > > 1. Can we specify names to documents hierarchy such as "therapeuticareas" > or "sites" while indexing. > 2. How

Index Deeply Nested documents and retrieve a full nested document in solr

Hello Team, Can someone please help to index the below sample json document into Solr. I have following queries on indexing multi level child document. 1. Can we specify names to documents hierarchy such as "therapeuticareas" or "sites" while indexing. 2. How can

Re: Why use a different analyzer for "index" and "query"?

People usually want to do some analysis during index time. This analysis should be considered 'expensive', compared to any single query run. You can think of it as indexing every day, over a 86400 second day, vs a 200 ms query time. Normally, you want to index as honestly as possible

Re: Why use a different analyzer for "index" and "query"?

It is very common for us to do more processing in the index analysis chain. In general, we do that when we want additional terms in the index to be searchable. Some examples: * synonyms: If the book title is “EMT” add “Emergency Medical Technician”. * ngrams: For prefix matching, generate all

Re: Why use a different analyzer for "index" and "query"?

When you want to do something different and index and query time. There, an answer that’s almost, but not quite, completely useless while being accurate ;) A concrete example is synonyms as have been mentioned. Say you have an index-time synonym definition of A,B,C These three tokens will be

Re: Why use a different analyzer for "index" and "query"?

; > In Solr's schema, I have come across field types that use a different logic > for "index" than for "query". To be clear, I"m talking about this block: > > positionIncrementGap="100"> > > > > > &

Re: Why use a different analyzer for "index" and "query"?

ion but fun use case: https://github.com/arafalov/solr-thai-test/blob/master/collection1/conf/schema.xml#L34-L55 (search phonetically mapped Thai text in English). Similarly, you may want to apply synonyms at query time only if you want to avoid diluting some relevancy. Or at index type to normali

Re: Why use a different analyzer for "index" and "query"?

Hi Steve I have a real-world use case. We don't apply a synonym filter at index time, but we do apply a managed synonym filter at query time. This allows content managers to add new synonyms (or remove existing ones) "on the fly" without having to reindex any documents. Thoma

RE: Why use a different analyzer for "index" and "query"?

Hi Steven, I can think of one case. If we have an index of database table or column names, e.g., words like 'THIS_IS_A_TABLE_NAME', we may want to split the name at the underscores when indexing (as well as keep the original), since the individual parts might be significant and

Why use a different analyzer for "index" and "query"?

Hi everyone, In Solr's schema, I have come across field types that use a different logic for "index" than for "query". To be clear, I"m talking about this block: Why would one want to not use the same

Re: Real time index data

es real time indexing of data in solr from DB. >> Approximately, 30 rows are updated in a second in DB. And I also want these >> to be updated in the index simultaneously. >> Is the Queuing mechanism like Rabbitmq helpful in my case? >> Please suggest the ways to achieve it. >> >> Regards, >> Tushar Arora

Re: Real time index data

second in DB. And I also want these > to be updated in the index simultaneously. > Is the Queuing mechanism like Rabbitmq helpful in my case? > Please suggest the ways to achieve it. > > Regards, > Tushar Arora

Real time index data

Hi, One of our use cases requires real time indexing of data in solr from DB. Approximately, 30 rows are updated in a second in DB. And I also want these to be updated in the index simultaneously. Is the Queuing mechanism like Rabbitmq helpful in my case? Please suggest the ways to achieve it

Re: How to forcefully open new searcher, in case when there is no change in Solr index

ote: > > I have a use case where none of the document in my solr index is changing but > I still want to open a new searcher through the curl api. > > On executing the below curl command > curl > "XXX.XX.XX.XXX:9744/solr/mycollection/update?openSearcher=true&com

How to forcefully open new searcher, in case when there is no change in Solr index

I have a use case where none of the document in my solr index is changing but I still want to open a new searcher through the curl api. On executing the below curl command curl "XXX.XX.XX.XXX:9744/solr/mycollection/update?openSearcher=true&commit=true" it doesn't open a new s

Re: Index files on Windows fileshare

> > On Fri, Jun 19, 2020 at 9:34 AM Fiz N wrote: > > > > Hello Solr experts, > > > > I am using standalone version of SOLR 8.5 on Windows machine. > > > > 1) I want to index all types of files under different directory in the > > file share. > > &

Re: Index files on Windows fileshare

be stored, you might be better off writing a small crawler in Java and using SolrJ to do the indexing. Good luck! Jason On Fri, Jun 19, 2020 at 9:34 AM Fiz N wrote: > > Hello Solr experts, > > I am using standalone version of SOLR 8.5 on Windows machine. > > 1) I want to inde

Re: Index file on Windows fileshare..

The program I pointed you to should take about an hour to make work. But otherwise, you can try the post tool: https://lucene.apache.org/solr/guide/7_2/post-tool.html Best, Erick > On Jun 23, 2020, at 8:45 AM, Fiz N wrote: > > Thanks Erick. Is there easy way of doing this? Index f

Re: Index file on Windows fileshare..

Thanks Erick. Is there easy way of doing this? Index files from windows share folder to SOLR. This is for POC only. Thanks Nadian. On Mon, Jun 22, 2020 at 3:54 PM Erick Erickson wrote: > Consider running Tika in a client and indexing the docs to Solr. > At that point, you have total c

Re: Index file on Windows fileshare..

ello Solr experts, > > I am using standalone version of SOLR 8.5 on Windows machine. > > 1) I want to index all types of files under different directory in the > file share. > > 2) I need to index absolute path of the files and store it solr field. I > need that info so tha

Index file on Windows fileshare..

Hello Solr experts, I am using standalone version of SOLR 8.5 on Windows machine. 1) I want to index all types of files under different directory in the file share. 2) I need to index absolute path of the files and store it solr field. I need that info so that end user can click and open the

Index files on Windows fileshare

Hello Solr experts, I am using standalone version of SOLR 8.5 on Windows machine. 1) I want to index all types of files under different directory in the file share. 2) I need to index absolute path of the files and store it solr field. I need that info so that end user can click and open the

Re: Solr 7.6 optimize index size increase

” on them, i.e. it’ll rewrite each large segment into a single new segment with all the deleted data removed thus gradually shrinking it. This happens automatically if you delete documents (update is a delete + add so counts), but you may have a significant percentage of deleted docs in your index

Re: Solr 7.6 optimize index size increase

://observer.wunderwood.org/ (my blog) > On Jun 17, 2020, at 4:12 AM, Raveendra Yerraguntla > wrote: > > Thank you David, Walt , Eric. > 1. First time bloated index generated , there is no disk space issue. one > copy of index is 1/6 of disk capacity. we ran into disk capacity after more &

Re: Solr 7.6 optimize index size increase

Thank you David, Walt , Eric. 1. First time bloated index generated , there is no disk space issue. one copy of index is 1/6 of disk capacity. we ran into disk capacity after more than 2  copies of bloated copies.2. Solr is upgraded from 5.*. in 5.* more than 5 segments is causing performance

Re: Solr 7.6 optimize index size increase

It Depends (tm). As of Solr 7.5, optimize is different. See: https://lucidworks.com/post/solr-and-optimizing-your-index-take-ii/ So, assuming you have _not_ specified maxSegments=1, any very large segment (near 5G) that has _zero_ deleted documents won’t be merged. So there are two scenarios

Re: Solr 7.6 optimize index size increase

For a full forced merge (mistakenly named “optimize”), the worst case disk space is 3X the size of the index. It is common to need 2X the size of the index. When I worked on Ultraseek Server 20+ years ago, it had the same merge behavior. I implemented a disk space check that would refuse to merge

Re: Solr 7.6 optimize index size increase

I cant give you a 100% true answer but ive experienced this, and what "seemed" to happen to me was that the optimize would start, and that will drive the size up by 3 fold, and if you out of disk space in the process the optimize will quit since, it cant optimize, and leave the live in

Solr 7.6 optimize index size increase

when optimize command is issued, the expectation after the completion of optimization process is that the index size either decreases or at most remain same. In solr 7.6 cluster with 50 plus shards, when optimize command is issued, some of the shard's transient or older segment files ar

Re: Index download speed while replicating is fixed at 5.1 in replication.html

Hello, The patch is to fix the display. It doesn't configure or limit the speed :) În mar., 16 iun. 2020 la 14:26, Shawn Heisey a scris: > On 6/14/2020 12:06 AM, Florin Babes wrote: > > While checking ways to optimize the speed of replication I've noticed > that > >

Re: Index download speed while replicating is fixed at 5.1 in replication.html

On 6/14/2020 12:06 AM, Florin Babes wrote: While checking ways to optimize the speed of replication I've noticed that the index download speed is fixed at 5.1 in replication.html. There is a reason for that? If not, I would like to submit a patch with the fix. We are using solr 8.3.1. Lo

Index download speed while replicating is fixed at 5.1 in replication.html

Hello, While checking ways to optimize the speed of replication I've noticed that the index download speed is fixed at 5.1 in replication.html. There is a reason for that? If not, I would like to submit a patch with the fix. We are using solr 8.3.1. Thanks, Florin Babes

Re: index join without query criteria

or probably -director_id:[* TO *] On Mon, Jun 8, 2020 at 10:56 PM Hari Iyer wrote: > Hi, > > It appears that a query criteria is mandatory for a join. Taking this > example from the documentation: fq={!join from=id fromIndex=movie_directors > to=director_id}has_oscar:true. What if I want to find

index join without query criteria

Hi, It appears that a query criteria is mandatory for a join. Taking this example from the documentation: fq={!join from=id fromIndex=movie_directors to=director_id}has_oscar:true. What if I want to find all movies that have a director (regardless of whether they have won an Oscar or not)? This

Re: Need help on handling large size of index.

Maybe your problems are in AWS land. > On May 22, 2020, at 3:45 AM, Modassar Ather wrote: > > Thanks Erick and Phill. > > We index data weekly once and that is why we do the optimisation and it has > helped in faster query result. I will experiment with a fewer segments

Re: Need help on handling large size of index.

Thanks Erick and Phill. We index data weekly once and that is why we do the optimisation and it has helped in faster query result. I will experiment with a fewer segments with the current hardware. The thing I am not clear about is although there is no constant high usage of extra IOPs other

Re: Need help on handling large size of index.

The optimal size for a shard of the index is be definition what works best on the hardware with the JVM heap that is in use. More shards mean smaller sizes of the index for the shard as you already know. I spent months changing the sharing, the JVM heap, the GC values before taking the system

Re: Need help on handling large size of index.

Please consider _not_ optimizing. It’s kind of a misleading name anyway, and the version of solr you’re using may have unintended consequences, see: https://lucidworks.com/post/segment-merging-deleted-documents-optimize-may-bad/ and https://lucidworks.com/post/solr-and-optimizing-your-index-take

Re: Need help on handling large size of index.

Thanks Shawn for your response. We have seen a performance increase in optimisation with a bigger number of IOPs. Without the IOPs we saw the optimisation took around 15-20 hours whereas the same index took 5-6 hours to optimise with higher IOPs. Yes the entire extra IOPs were never used to full

Re: Need help on handling large size of index.

Thanks Phill for your response. Optimal Index size: Depends on what you are optimizing for. Query Speed? Hardware utilization? We are optimising it for query speed. What I understand even if we set the merge policy to any number the amount of hard disk will still be required for the bigger

Re: Need help on handling large size of index.

On 5/20/2020 11:43 AM, Modassar Ather wrote: Can you please help me with following few questions? - What is the ideal index size per shard? We have no way of knowing that. A size that works well for one index use case may not work well for another, even if the index size in both cases

Re: Need help on handling large size of index.

In my world your index size is common. Optimal Index size: Depends on what you are optimizing for. Query Speed? Hardware utilization? Optimizing the index is something I never do. We live with about 28% deletes. You should check your configuration for your merge policy. I run 120 shards, and I

Re: Need help on handling large size of index.

In my world your index size is common. Optimal Index size: Depends on what you are optimizing for. Query Speed? Hardware utilization? Optimizing the index is something I never do. We live with about 28% deletes. You should check your configuration for your merge policy. I run 120 shards, and I

Need help on handling large size of index.

Hi, Currently we have index of size 3.5 TB. These index are distributed across 12 shards under two cores. The size of index on each shards are almost equal. We do a delta indexing every week and optimise the index. The server configuration is as follows. - Solr Version : 6.5.1 - AWS

Re: Index using CSV file

Am 18.04.2020 um 17:43 schrieb Jörn Franke : > >  > This you don’t do via the Solr UI. You have many choices amongst others > 1) write a client yourself that parses the csv and post it to the standard > Update handler > https://lucene.apache.org/solr/guide/8_4/uploading-data-with-in

Re: Index using CSV file

This you don’t do via the Solr UI. You have many choices amongst others 1) write a client yourself that parses the csv and post it to the standard Update handler https://lucene.apache.org/solr/guide/8_4/uploading-data-with-index-handlers.html 2) use the Solr post tool https://lucene.apache.org

Index using CSV file

Hi, I'm trying to import data from CSV file from Solr UI and I am completely new to Solr. Please provide the necessary configurations to achieve this.

Re: ReversedWildcardFilter - should it be applied only at the index time?

dd &debug=query? That should tell you…. Best, Erick On Apr 15, 2020, at 2:40 PM, TK Solr wrote: Thank you. Is there any harm if I use it on the query side too? In my case it seems working OK (even with withOriginal="false"), and even faster. I see the query pars

Re: ReversedWildcardFilter - should it be applied only at the index time?

;), and even faster. > I see the query parser code is taking a look at index analyzer and applying > ReversedWildcardFilter at query time. But I didn't > quite understand what happens if the query analyzer also uses > ReversedWildcardFilter. > > On 4/15/20 1:51 AM, Col

Re: ReversedWildcardFilter - should it be applied only at the index time?

Thank you. Is there any harm if I use it on the query side too? In my case it seems working OK (even with withOriginal="false"), and even faster. I see the query parser code is taking a look at index analyzer and applying ReversedWildcardFilter at query time. But I didn't quite

Re: Solr index size has increased in solr 7.7.2

i wouldnt worry about the index size until you get above a half terabyte or so. adding doc values and other features means you sacrifice things that dont matter, like size. memory and ssd's are cheap. On Wed, Apr 15, 2020 at 1:21 PM Rajdeep Sahoo wrote: > Hi all > We are migratin

Solr index size has increased in solr 7.7.2

Hi all We are migrating from solr 4.6 to solr 7.7.2. In solr 4.6 the size was 2.5 gb but here in solr 7.7.2 the solr index size is showing 6.8 gb with the same no of documents. Is it expected behavior or any suggestions how to optimize the size.

Re: ReversedWildcardFilter - should it be applied only at the index time?

You only need apply it in the index analyzer: https://lucene.apache.org/solr/8_4_0/solr-core/org/apache/solr/analysis/ReversedWildcardFilterFactory.html If it appears in the index analyzer, the query part of it is automatically applied at query time. The ReversedWildcardFilter indexes *every

Re: ReversedWildcardFilter - should it be applied only at the index time?

I experimented with the index-time only use of ReversedWildcardFilter and the both time use. My result shows using ReverseWildcardFilter both times runs twice as fast but my dataset is not very large (in the order of 10k docs), so I'm not sure if I can make a conclusion. On 4/8/20 2:

ReversedWildcardFilter - should it be applied only at the index time?

In the usage example shown in ReversedWildcardFilter in Solr Ref Guide, and only usage find in managed-schema to define text_general_rev, the filter is used only for indexing.   positionIncrementGap="1

RE: No files to download for index generation

ather than as INFO or WARN ? Please advise -Original Message- From: Oakley, Craig (NIH/NLM/NCBI) [C] Sent: Wednesday, March 11, 2020 5:18 PM To: solr-user@lucene.apache.org Subject: RE: No files to download for index generation I wanted to ask *again* whether anyone has any insight rega

  1   2   3   4   5   6   7   8   9   10   >