[
https://issues.apache.org/jira/browse/SOLR-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342400#comment-16342400
]
David Smiley commented on SOLR-11066:
-------------------------------------
Solr has some conventions here already... "TZ" is Solr's timezone parameter.
It has been exclusively used for date math semantics alone – all times are
fully unambiguous with Z==UTC. I've working on Time Routed Aliases with
[~gus_heck] and we followed this convention. I guess I'm okay with allowing
startTime to not have a trailing 'Z' provided that in this circumstance, we
insist that TZ is provided.
graceTime should probably be renamed graceDuration since it is not a time
(startTime is a time). I like the readability of using date math. With Time
Routed Aliases there's a little internal setting "max-future-ms" that is in
milliseconds but I hesitated a bit on wether to use date math. Maybe we should
have.
It's not clear to me looking at the patch how these ScheduledTriggers are
created. Can you please explain? I was anticipating some new API call to
create the trigger.
> Implement a scheduled trigger
> -----------------------------
>
> Key: SOLR-11066
> URL: https://issues.apache.org/jira/browse/SOLR-11066
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: SOLR-11066.patch, SOLR-11066.patch
>
>
> Implement a trigger that runs on a fixed interval say every 1 hour or every
> 24 hours starting at midnight etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
