Get only year from a date field for a copy field ?

Hi Solr Team, Is it possible to create a copy field where the source is a date-time field to extract only the year ? I have 2024-07-01T253:59:59Z for the date field and store/index a copy field with only 2024. The goal is to have faceting only on Year information. Note: I haven't the po

Re: Searching for synonyms

I changed my configuration as suggest, but it didn't help. I can't search for tera* instead of terra*, I think there is also another problem. kind regards Carsten Am 27.06.24, 17:50 schrieb "Marcus Bergner" mailto:marcus.berg...@vizrt.com.inva>LID>: I think you

Re: Get only year from a date field for a copy field ?

Hi Bruno, Did you consider using a range facet with gap being 1 year? If that works for you, you can avoid reindexing altogether. https://solr.apache.org/guide/8_1/json-facet-api.html Try specifying gap as "1YEARS" or "+1YEARS" (I forgot if plus sign was required or not) Sincerely Ufuk Yilm

Re: Problem with atomic updates after upgrading from 8.11 to 9.6

Hi Jeremy, Based on the information you provided I would say that your price_list_url is recognized as an object instead of a field update. Depending on the way you update your document(s), this may succeed and do what you want, succeed and create flattened documents or fail. A flattened object wo

Re: Problem with atomic updates after upgrading from 8.11 to 9.6

Hi Christos, thanks for the reply. I am using the /update endpoint. If I change to /update/json/docs, it does what you suggest and creates a flattened document. But that isn't what I want. Somewhat strangely, I only have one collection that is acting this way - atomic updates on other collection

RE: Get only year from a date field for a copy field ?

Hi Ufuk, Thanks for the tips ! It works fine with this : http://localhost:8983/solr/db001/select? facet.contains.ignoreCase=true &fl=ap,in &indent=true &q.op=OR &q=ti%3Atreat* &rows=1 &facet=true &facet.range.gap=%2B1YEAR (the GAP)

Re: Problem with atomic updates after upgrading from 8.11 to 9.6

With a correctly configured configset and a collection with data in it, I can only reproduce the error if there are documents that are wrongly indexed. In that situation, fixing the documents in the collection (so that they are no flattened documents) and reloading / reindexing the affected collect

Re: Problem with atomic updates after upgrading from 8.11 to 9.6

I can reproduce the error on a fresh collection with only a single document added, so it may be something related to my schema. I think at this point I'm about ready to punt and just do non-atomic full updates for this scenario, which actually won't be that difficult. Thanks for your suggestions!