That looks like a nice workaround, I'll give it a try, thanks a lot Pat. Cheers.
2016-12-15 18:33 GMT+01:00 Pat Ferrel <[email protected]>: > Yes retrain is required since the dates are attached to items in the model > and must be understood by an Elasticsearch query, therefore indexed by ES. > You could bypass the `pio train` and modify the Elasticsearch model > directly but send the $set also so things will stay synced on the next `pio > build` > > Examine the model, which is in the indexName (defined in engine.json) of > Elasticsearch and it should be obvious how they are stored. See > Elasticsearch docs for browsing the index and how to change > properties/fields of an item/doc > > > > On Dec 15, 2016, at 8:58 AM, Marcos López <[email protected]> wrote: > > Greetings, > > I'm making a pio deployment and I have some doubts about the use of the > availableDate and expirationDate parameters. > > I have some items that change their available dates quite often, so they > may not be available for some time and then come back. > > Do $set events need a retraining? Could I just update the avialableDate > and expireDate properties and get them to show up without training? > > Thanks a lot, Marcos. > >
