My apologies first for posting in the wrong forum as I thought they are
internally using Solr and the the process is all same when it comes to filed
mapping etc.
And really appreciate your patience in assisting me. Thank you once again.
--
View this message in context:
http://lucene.472066.n3.
It would have been very helpful if you'd mentioned Fusion earlier.
Fusion is a Lucidworks product, not something the Solr community can
be expected to troubleshoot. I suggest you contact Lucidworks support
for help with that.
Best,
Erick
On Sun, Jul 30, 2017 at 11:56 AM, MKrishna wrote:
> The a
The actual setup is :
Lucid works Fusion 3.1.0 (installed on a Linux machine) is the latest
upgrade we did for the search index from fusion 2.4.Also with 2.4 we had the
schema less mode.
Basically we are indexing the outlook files stored in a folder via smb as
input to Lucid fusion.
My applica
Version 3.1 of _what_? Certainly not Solr as schemaless is not in any
3x version of Solr. So it sounds like you changed some other part of
your system. Can't help you there.
And I do not recommend schemaless mode for production. Use it to find
out what kinds of data you get, but then I'd advise yo
We are using the schema less mode trying to parse outlook(.msg) files in an
smb.
and I get to see the properties of the .msg file(date_created fields )
stored in dynamic fields date_Created_s and date_created_t.
This change is seen only after upgrading the version to 3.1 as the older
versions(2.0*
It's right there in the reference guide:
https://cwiki.apache.org/confluence/display/solr/Copying+Fields
But that's not what I was talking about, you've got it backwards
What you haven't really told us is why the data is being sent to
date_created in the first place. How are you parsing the fi
date_created field is being indexed as a string and text general making it
difficult to apply date range queries
date_created_s and date_created_t are the extensions and trying to copy them
to *_tdate is throwing an error.
"copyFields can take glob-type source specifications if that helps. "
Can
bq: We want to use a copy field as a source for another copy field.
As asked, this is not supported. You can copy the same source field to
multiple copy fields however.
copyFields can take glob-type source specifications if that helps.
It would help if you gave concrete examples. You say "date c
