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.
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
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*
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
We want to use a copy field as a source for another copy field.
The problem is source field is from a text (dynamic field ) and
destination field should be date
tried changing the dynamic field datatype but it throws error.
ideally my search index data source is outlook PST files as the index
Hi all,
I’m using Lucence Solr (Lucidworks ) as the search index and its a
schemaless search engine to index outlook files.
I have been using it since version 2.0.* and have an issue with querying
dates.
The older versions were mapping( date_created, mail from_date etc) to date
datatype making
