IntField is not indexing properly - field properties changed to "just stored"

2015-12-17 Thread Kumaran Ramasubramanian
Hi All, i am using lucene 4.10.4. i am using below code to index IntField. All properties of IntField is vanished except stored. Any help is much appreciated. IndexWriterConfig iwc = new IndexWriterConfig(Version.LUCENE_4_10_4, new > ClassicAnalyzer(Version.LUCENE_30, new StringReader(""))); > i

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Kumaran Ramasubramanian
yes. All fields are stored in index. so sounds like working. Thanks a lot jack :-) Nice to meet you here :-) -- ​ Kumaran R​ On Fri, Dec 18, 2015 at 12:49 AM, Jack Krupansky wrote: > You could certainly read your stored values from your current index and > then write new documents to a new i

Re: Searching for "iso surface", and looking for "isosurface"

2015-12-17 Thread Jack Krupansky
Unfortunately there is no general support for this feature. But you can approximate it if you have a relatively small set of compound terms using the DictionaryCompoundWordTokenFilterFactory: http://lucene.apache.org/core/5_4_0/analyzers-common/org/apache/lucene/analysis/compound/DictionaryCompound

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Jack Krupansky
You could certainly read your stored values from your current index and then write new documents to a new index and then use the new index. That's if all of the indexed field values are stored. -- Jack Krupansky On Thu, Dec 17, 2015 at 2:10 PM, Kumaran Ramasubramanian wrote: > Hi Jack Krupansky

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Kumaran Ramasubramanian
Hi Jack Krupansky Thanks for the reply. That will work fine. But i am trying to use the stored values instead of hitting database for reindex. Isn't it better way to reindex? Any inputs? -- ​Kumaran R On Thu, Dec 17, 2015 at 11:50 PM, Jack Krupansky wrote: > Delete the full index and creat

Searching for "iso surface", and looking for "isosurface"

2015-12-17 Thread Xiaolong Zheng
Hi All, I want to know what's the common way to implement the searching with whitespace removal. For example, if I searching "iso surface" in google, it not only search for "iso" or "surface", but also have a search for "isosurface". Is that just simply add another search clause by removing the w

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Jack Krupansky
Delete the full index and create from scratch with the correct field type, re-adding all documents. Any remnants of the old field must be removed. -- Jack Krupansky On Thu, Dec 17, 2015 at 11:48 AM, Kumaran R wrote: > While Reindexing only am facing this problem. > > Just to confirm what do you

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Kumaran R
While Reindexing only am facing this problem. Just to confirm what do you mean by reindex. You mean "delete and add" for all documents by taking data one by one right?? Sent from Phone > On 17-Dec-2015, at 8:53 PM, Jack Krupansky wrote: > > The standard answer is that you need to reindex all of

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Jack Krupansky
The standard answer is that you need to reindex all of your data. -- Jack Krupansky On Thu, Dec 17, 2015 at 6:10 AM, Kumaran Ramasubramanian wrote: > Dear All > > i am using lucene 4.10.4. Is there any more information i missed to > provide? Please let me know. > > > -- > Kumaran R*​* > > > >

Re: propagate Query.rewrite call to super.rewrite after 5.4 upgrade

2015-12-17 Thread Alan Woodward
You may be able to do something along the lines of PayloadScoreQuery? That overrides the scorer to factor in the value of payloads at each position. In fact, a generic PositionScoringQuery would be a nice addition to the span queries. Alan Woodward www.flax.co.uk On 17 Dec 2015, at 13:58, M

RE: propagate Query.rewrite call to super.rewrite after 5.4 upgrade

2015-12-17 Thread Markus Jelsma
Hello Adrian, I haven't implemented rewrite at all. I think something else is wrong in my approach and adding to the confusion. I override protected AcceptStatus acceptPosition(Spans spans). In there, i conditionally call setBoost() myself because originally i wanted to decrease the boost for e

Re: propagate Query.rewrite call to super.rewrite after 5.4 upgrade

2015-12-17 Thread Adrien Grand
Hi Markus, This is indeed related to LUCENE-6590: query boosts are now applied with BoostQuery and if Query.setBoost is called on a query, its rewrite implementation needs to rewrite to a BoostQuery. You can do that by prepending the following to your rewrite(IndexReader) implementation: if (getB

propagate Query.rewrite call to super.rewrite after 5.4 upgrade

2015-12-17 Thread Markus Jelsma
Hi, Apologies for the cross post. We have a class overridding SpanPositionRangeQuery. It is similar to a SpanFirst query but it is capable of adjusting the boost value with regard to distance. With the 5.4 upgrade the unit tests suddenly threw the following exception: Query class org.GrSpanFir

Re: Need change one field type from IntField to String including indexOptions to store positions & Norms

2015-12-17 Thread Kumaran Ramasubramanian
Dear All i am using lucene 4.10.4. Is there any more information i missed to provide? Please let me know. -- Kumaran R*​* On Wed, Dec 16, 2015 at 10:35 PM, Kumaran Ramasubramanian < kums@gmail.com> wrote: > > Hi All, > > Previous Post - > http://www.gossamer-threads.com/lists/lucene/ja