Hi Uwe
Looking at the magnitude of the API changes from Lucene 4 to 6, I don't
think we'll ever be able to upgrade. It seems the API has been modified
to a large extent.
Is there any chance that the bug fixes will back ported to the 4.0 branch?
Jamie
Hi,
> - Alternatively you can use UninvertingReader from the misc module and
> wrap your index reader. This "emulates" the DocValues APIs on indexes
> without DocValues. Internally it uses the old FieldCache code to do this. This
> has the same problems as earlier Lucene versions: Heavy heap usag
In Lucene you have to use the new DocValues fields (available since 4.0) to
sort on.
For backwards compatibility, you can still use the older "uninversion" hack
(also known as "Field Cache"). In Lucene 5 and 6 this part was removed from
Lucene Core. To sort, you have 2 options:
- Reindex your
Depending on what you are looking for everything you need is in the docs.
The book just has a good structure a problem you will face is the book is
not up to date with the latest API changes but the main concepts are there
so if you want to read the Docs you can always do that of you want some
insi
Okay. Thanks a lot for your suggestion.
When will you think is the right time to start reading the *lucene's
official apache docs ?*
Thanks.
On Mon, Apr 25, 2016 at 11:11 PM, Taher Galal
wrote:
> I would say Start with reading lucene in action
> On 25 Apr 2016 19:39, "Prateek Singhal" wrote:
I would say Start with reading lucene in action
On 25 Apr 2016 19:39, "Prateek Singhal" wrote:
> Hi Folks,
>
> I am very new to Lucene. Used it in a couple of projects but haven't really
> got into the insights of how it works and
> *never Deep Dived into its code-base*
> Just for a head-start I
Hi Folks,
I am very new to Lucene. Used it in a couple of projects but haven't really
got into the insights of how it works and
*never Deep Dived into its code-base*
Just for a head-start I want some guidance from *all the smart folks* on
this group regarding *which knowledge source will be a good
Thanks for going to fix the stale docs.
Torsten
Am Montag, den 25.04.2016, 11:09 -0400 schrieb Michael McCandless:
> The Lucene level javadocs are definitely stale ... I'll fix.
>
>
> You should separately add a SortedDocValuesField if you also need to
> sort on this field.
>
> Mike McCandless
Hi Erick,
i guess you've muddled the lists - this is lucenes one, not solr. I know
how to define it in solr but that wasn't the question as i am using pure
lucene and it did not work as expected from the javadocs there.
Cheers
Torsten
--
Yep.. adding a SortedDocValuesField did work for me! thanks..
On Mon, Apr 25, 2016 at 8:39 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> The Lucene level javadocs are definitely stale ... I'll fix.
>
> You should separately add a SortedDocValuesField if you also need to sort
> on t
Hi Ahmet,
MemoryIndex is exactly what I was looking for.
Thanks a lot for the quick response :)
2016-04-25 15:40 GMT+01:00 Ahmet Arslan :
> Hi,
>
> MemoryIndex is used for that purpose.
>
> Please see :
>
> https://github.com/flaxsearch/luwak
>
>
> https://www.elastic.co/guide/en/elasticsearch/
The Lucene level javadocs are definitely stale ... I'll fix.
You should separately add a SortedDocValuesField if you also need to sort
on this field.
Mike McCandless
http://blog.mikemccandless.com
On Fri, Mar 6, 2015 at 5:04 AM, Torsten Krah wrote:
> Hi,
>
> looking at the JavaDoc of StringFi
This works fine for me in a current Solr (5x). What version are you using?
Note that _any_ field you use for sorting _must_ be indexed="true" or, in
recent Solrs, docValues="true", just like any other field. You can't
sort on a field that
only has stored='"true" which is the only bit of the field
Hi,
MemoryIndex is used for that purpose.
Please see :
https://github.com/flaxsearch/luwak
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-percolate.html
http://lucene.apache.org/core/6_0_0/memory/index.html?org/apache/lucene/index/memory/MemoryIndex.html
Ahmet
On Mo
Hi all,
Is it possible to evaluate if a document satisfies a query? Of course it
can be done indexing the document in a RAMIndex and querying it, but I
wonder if it is possible to do it in a more efficient way.
Thanks,
--
Andrés de la Peña
Vía de las dos Castillas, 33, Ática 4, 3ª Planta
28224
Hi,
unfortunately i did not and no one did answered to this yet - although
javadoc states it should work it does not.
In the meantime i've used my own custom field but still i am interested
on a solution to this.
Lucene 6 still does have the same javadoc:
https://lucene.apache.org/core/6_0_0/cor
16 matches
Mail list logo
