[
https://issues.apache.org/jira/browse/AURORA-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431648#comment-15431648
]
Stephan Erb commented on AURORA-1734:
-------------------------------------
Your point that we jumped the gun on a 'what-if' is probably correct.
However, now that this feature is released, we have no other way than to
proceed in a backwards compatible manner. This implies that we cannot drop the
prefix immediately, but would have to make it configurable in order to change
it in the future release eventually.
I would therefore propose to proceed with a minimal viable patch to make the
prefix configurable, and reevaluate that decision in the future if necessary.
> Configurable Metadata prefix
> ----------------------------
>
> Key: AURORA-1734
> URL: https://issues.apache.org/jira/browse/AURORA-1734
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Renan DelValle
> Assignee: Renan DelValle
> Priority: Trivial
>
> Currently, a prefix ("org.apache.aurora.metadata.") is injected into the
> metadata key in the scheduler. It would be beneficial to allow users to set
> their own metadata prefix (including an empty string).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
