dynamically adding fields to the schema, you
> will need to do that anyway.
>
> Regards,
>Alex.
>
> On 27 February 2015 at 08:53, Makailol Charls <4extrama...@gmail.com>
> wrote:
> >
> >
> > add-unknown-fields-to-the-schema
> >
> >
>
>
>
>
> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
> http://www.solr-start.com/
>
Hi,
As suggested, we could manage to activate the document expiration using TTL
by shifting the newly added URP setting in the starting of the
add-unknown-fields-to-the-schema URP. That populates the "expire_at_dt"
field and makes document to expire after defined TTL.
Many Thanks,
Makailol
On Fr
Hi
Thanks for the reply.
I am just beginning with the solr, so not much familiar with the settings
of the solr. I have created solr "collection1" core with the following
command.
bin/solr create -c collection1
Then modified the managed-schema file to add required field definitions
There were n
L.
>
> So, recheck your solrconfig.xml. Or add another explicit field
> population inside the chain, just like the example did with
> TimestampUpdateProcessorFactory :
> https://lucidworks.com/blog/document-expiration/
>
> Regards,
> Alex.
>
> On 26 February 2
.
Thanks,
Makailol
On Thu, Feb 26, 2015 at 6:22 PM, Makailol Charls <4extrama...@gmail.com>
wrote:
> Hi
>
> Thanks for your quick reply.
>
> " since your time_to_live_s and expire_at_dt fields are both
> stored, can you confirm that a expire_at_dt field is getting popular
Hi
Thanks for your quick reply.
" since your time_to_live_s and expire_at_dt fields are both
stored, can you confirm that a expire_at_dt field is getting popularted by
the update processor by doing as simple query for your doc (ie
q=id:10seconds) "
No, expire_at_dt field does not get populated w
Hello,
We are trying to add documents in solr with ttl defined(document expiration
feature), which is expected to expire at specified time, but it is not.
Following are the settings we have defined in solrconfig.xml and
managed-schema.
solr version : 5.0.0
*solrconfig.xml*
--
