org.apache.lucene.util.packed.DirectReader$DirectPackedReader48.get(DirectReader.java:305)
... 35 more
On Fri, May 11, 2018 at 1:15 AM, Adrien Grand wrote:
> Can you share the full stack trace?
>
> Le ven. 11 mai 2018 à 04:19, Tom Hirschfeld a
> écrit :
>
> > Hey All,
> > I h
to address this issue but I have
been unable to find out whats going on. Any hint as to what might be
happening here?
Best,
Tom Hirschfeld
s this compatible? Are we able to store our index in
HDFS and read from a spark job?
Best,
Tom Hirschfeld
sort about 200 results. My specific questions are, for our use case,
how do these two fields differ in:
1) total index size
2) query time performance/impact on sorting
3) any other "gotchas" I may not have thought of yet
Thanks for your time & assistance!
Best,
Tom Hirschfeld
ed if it
exists. Is there a recommended way to support indexing and searching of
polygons (building footprint sized polygons, not huge ones)? If so what is
the currently recommended API to use? We are currently thinking about using
the s2cell library from google.
Best,
Tom Hirschfeld
segment
per cpu in prod? 1 segment per core in prod? Something else?
Best,
Tom Hirschfeld
Once again, thanks for your help.
Best,
Tom Hirschfeld
On Thu, May 18, 2017 at 4:22 AM, Uwe Schindler wrote:
> Hi,
> Are you sure that the term index is the problem? Even with huge indexes
> you never need 65 good of heap! That's impossible.
> Are you sure that your problem is not
is issue? If so, how do
I got about loading an alternative codec and configuring it to my needs?
I'm having trouble finding docs/examples of how this is used in the real
world so even if you point me to a repo or docs somewhere I'd appreciate
it.
Thanks!
Best,
Tom Hirschfeld
? If so, how do
I got about loading an alternative codec and configuring it to my needs?
I'm having trouble finding docs/examples of how this is used in the real
world so even if you point me to a repo or docs somewhere I'd appreciate
it.
Thanks!
Best,
Tom Hirschfeld
