Thanks for the reply, will find out more about it.
Currently I am able to retrieve the normal Metadata of the email, but not
the Metadata of the attachments which are part of the contents in the EML
file, which looks something like this.
--d8b77b057d59ca19--
--d8b77e057d5
I'd strongly recommend rolling your own ingest code. See Erick's
superb: https://lucidworks.com/post/indexing-with-solrj/
You can easily get attachments via the RecursiveParserWrapper, e.g.
https://github.com/apache/tika/blob/master/tika-parsers/src/test/java/org/apache/tika/parser/RecursiveParse
>
> If you think about it, having a shard with 3 replicas on top of a file
system that does 3x replication seems a little excessive!
https://issues.apache.org/jira/browse/SOLR-6305 should help here. I can
take a look at merging the patch since looks like it has been helpful to
others.
Kevin Ri
Hi Kyle - Thank you.
Our current index is split across 3 solr collections; our largest
collection is 26.8TBytes (80.5TBytes when 3x replicated in HDFS) across
100 shards. There are 40 machines hosting this cluster. We've found
that when dealing with large collections having no replicas (but l
Not sure if this is possible, but why not create a query handler in Solr with
any custom query and you use that as ping replacement ?
> Am 02.08.2019 um 15:48 schrieb dinesh naik :
>
> Hi all,
> I have few clusters with huge data set and whenever a node goes down its
> not able to recover due t
Hi all,
I have few clusters with huge data set and whenever a node goes down its
not able to recover due to below reasons:
1. ping request handler is taking more than 10-15 seconds to respond. The
ping requesthandler however, expects it will return in less than 1 second
and fails a requestrecove
Was I correct in my description yesterday (which I am pasting in below)? That
you are using a hash based on the "solr" account name and expecting that to
work if you change the account name but not the hash?
Am I correct in assuming that everything other than security-edit functions
currently w
Hi Joe,
We fought with Solr on HDFS for quite some time, and faced similar issues
as you're seeing. (See this thread, for example:"
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201812.mbox/%3cCABd9LjTeacXpy3FFjFBkzMq6vhgu7Ptyh96+w-KC2p=-rqk...@mail.gmail.com%3e
)
The Solr lock files
Thank you. No, while the cluster is using Cloudera for HDFS, we do not
use Cloudera to manager the solr cluster. If it is a
configuration/architecture issue, what can I do to fix it? I'd like a
system where servers can come and go, but the indexes stay available and
recover automatically. I
I just checked also the output of the telnet commands - for conf it is
different for standalone compared to ensemble, will put it later in the Jira
> Am 02.08.2019 um 03:46 schrieb Zheng Lin Edwin Yeo :
>
> Yes, I tried with space and the same error occurs.
>
> I have also tried to put * , but
Telnet is working correct. The status endpoint seem to report the error that is
displayed in the UI.
I don’t see any obvious in the code, but it might not be working for more than
one node, but i am not sure exactly why.
I could not find the log line there with „membership: check 4lw“ in the so
Try the Apache Tika mailing list.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 2. aug. 2019 kl. 05:01 skrev Zheng Lin Edwin Yeo :
>
> Hi,
>
> Does anyone knows if this can be done on the Solr side?
> Or it has to be done on the Tika side?
>
> Regards,
> Edwin
>
You can use the configset API:
https://lucene.apache.org/solr/guide/7_7/configsets-api.html
I don’t recommend to use Schema.xml , but managed Schemas:
https://lucene.apache.org/solr/guide/6_6/schema-api.html
For people new to Solr I generally recommend to read a recent book about Solr
from begi
>From what I see, you are trying to change your own user's password. If I
remembered correctly this might not be allowed, which is why you are
getting the "Unauthorized request" error.
You can try to create another user with admin role as well, and to change
your existing user's password from the
14 matches
Mail list logo
