Hi,
I recently noticed that the SOLR javadocs hosted by lucene are not linkable as
the „package-list“ file is not downloadable. Is this on purpose?
$ curl https://lucene.apache.org/solr/8_4_0/solr-solrj/package-list
301 Moved Permanently
Moved Permanently
The document has moved https://lucene
Am 02.08.2018 um 12:06 schrieb Thomas Scheffler
> :
>
> Hi,
>
> we noticed a memory leak in a rather small setup. 40.000 metadata documents
> with nearly as much files that have „literal.*“ fields with it. While 7.2.1
> has brought some tika issues (due to a beta version) the rea
ieb Vincenzo D'Amore :
>
> Not clear if you had experienced an OOM error.
>
> On Thu, Aug 2, 2018 at 12:06 PM Thomas Scheffler <
> thomas.scheff...@uni-jena.de> wrote:
>
>> Hi,
>>
>> we noticed a memory leak in a rather small setup. 40.000 metadata
>>
Hi,
we noticed a memory leak in a rather small setup. 40.000 metadata documents
with nearly as much files that have „literal.*“ fields with it. While 7.2.1 has
brought some tika issues (due to a beta version) the real problems started to
appear with version 7.3.0 which are currently unresolved
Hi,
we noticed the same problems here in a rather small setup. 40.000 metadata
documents with nearly as much files that have „literal.*“ fields with it. While
7.2.1 has brought some tika issues the real problems started to appear with
version 7.3.0 which are currently unresolved in 7.4.0. Memor
Hi,
I have metadata and file indexed in solr. All have a different id of
cause but share the same value for "returnId" if they belong to the same
metadata that describes a bunch of files (1:n).
When I start a search. I usually use grouping instead of join queries to
keep the information wher
Hi,
I noticed that not only SOLR does not deliver a WAR file anymore but
also advices not to try to provide a custom WAR file that can be
deployed anymore as future version may depend on custom jetty features.
Until 4.10. we were able to provide a WAR file with all the plug-ins we
need for e
Am 21.05.2014 15:07, schrieb Joel Bernstein:
You may want to investigate the group.func option. This would allow you to
plug in your own logic to return the group by key. I don't think there is
an existing function that does exactly what you need so you may have to
write a custom function.
I th
Hi,
I have a special case of grouping multivalued fields and I wonder if
this is possible with SOLR.
I have a field "foo" that is generally multivalued. But for a restricted
set of documents this field has one value or is not present. So normally
grouping should work.
Sadly SOLR is failing
Am 20.05.2014 14:11, schrieb Jack Krupansky:
To be clear, you cannot update a single document of a nested document
in place - you must reindex the whole block, parent and all children.
This is because this feature relies on the underlying Lucene block
join feature that requires that the documents
nice, too.
Does anyone have information how nested document support evolve in
future releases of SOLR?
kind regards,
Thomas
19.05.2014 10:37 пользователь "Thomas Scheffler" <
thomas.scheff...@uni-jena.de> написал:
Hi,
I plan to use nested documents to group some
and has some caveats:
http://blog.griddynamics.com/2013/09/solr-block-join-support.html
regards,
Thomas
On May 18, 2014, at 11:36 PM, Thomas Scheffler
wrote:
Hi,
I plan to use nested documents to group some of my fields
art0001 My first
article art0001-foo Smith, John author
art0001
Hi,
I plan to use nested documents to group some of my fields
art0001
My first article
art0001-foo
Smith, John
author
art0001-bar
Power, Max
reviewer
This way can ask for any documents that are reviewed by Max Power.
However to simplify update and deletes
Am 04.03.2014 07:21, schrieb Thomas Scheffler:
Am 27.02.2014 09:15, schrieb Shawn Heisey:
On 2/27/2014 12:49 AM, Thomas Scheffler wrote:
What problems have you seen with mixing 4.6.0 and 4.6.1? It's possible
that I'm completely ignorant here, but I have not heard of any.
Ac
Am 27.02.2014 09:15, schrieb Shawn Heisey:
On 2/27/2014 12:49 AM, Thomas Scheffler wrote:
What problems have you seen with mixing 4.6.0 and 4.6.1? It's possible
that I'm completely ignorant here, but I have not heard of any.
Actually bug reports arrive me that sound like
"
Am 03.03.2014 19:12, schrieb Smiley, David W.:
The main reference for this approach is here:
http://wiki.apache.org/solr/SpatialForTimeDurations
Hoss’s illustrations he developed for the meetup presentation are great.
However, there are bugs in the instruction — specifically it’s important
to s
Am 01.03.14 18:24, schrieb Erick Erickson:
I'm not clear what you're really after here.
Solr certainly supports ranges, things like time:[* TO date_spec] or
date_field:[date_spec TO date_spec] etc.
There's also a really creative use of spatial (of all things) to, say
answer questions involving
Hi,
I am in the need of range types in SOLR - similar to PostgreSQL:
https://wiki.postgresql.org/images/7/73/Range-types-pgopen-2012.pdf
My schema should allow approximate dates and queries on that. When
having a single such date per document one can split this information
into two separate fi
Am 27.02.2014 08:04, schrieb Shawn Heisey:
On 2/26/2014 11:22 PM, Thomas Scheffler wrote:
I am one developer of a repository framework. We rely on the fact, that
"SolrJ generally maintains backwards compatibility, so you can use a
newer SolrJ with an older Solr, or an older SolrJ with a
Hi,
I am one developer of a repository framework. We rely on the fact, that
"SolrJ generally maintains backwards compatibility, so you can use a
newer SolrJ with an older Solr, or an older SolrJ with a newer Solr." [1]
This statement is not even true for bugfix releases like 4.6.0 -> 4.6.1.
Am 27.11.2013 09:58, schrieb Paul Libbrecht:
Thomas,
our experience with Curriki.org is that evaluating what I call the
"related documents" is a procedure that needs access to the complete
content and thus is run at the DB level and no thte sold-level.
For example, if a user changes a part of i
Hi,
I am relatively new to SOLR and I am looking for a neat way to implement
weak documents with SOLR.
Whenever a document is updated or deleted all it's dependent documents
should be removed from the index. In other words they exist as long as
the document exist they refer to when they were
22 matches
Mail list logo
