[
https://issues.apache.org/jira/browse/CALCITE-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775021#comment-16775021
]
Stamatis Zampetakis commented on CALCITE-2859:
----------------------------------------------
[~julianhyde], [~asereda] I added a quick implementation for this. Should we
continue like this or re-use the mechanism in SaffronProperties? Does it make
sense to unify calcite system properties with saffron properties? (Where does
the name Saffron comes from by the way?)
> Centralize Calcite system properties
> ------------------------------------
>
> Key: CALCITE-2859
> URL: https://issues.apache.org/jira/browse/CALCITE-2859
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.18.0
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.19.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently there are various system (jvm) properties exploited by Calcite
> which are distributed all over the codebase. System properties are part of
> the public API so they should be easily accessible and well documented.
> The goal is to centralize all system properties with the "calcite" prefix
> under a common class/interface/enum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
