[
https://issues.apache.org/jira/browse/SPARK-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338457#comment-14338457
]
Thomas Graves commented on SPARK-3508:
--------------------------------------
I wasn't suggesting renaming existing configs, I was proposing for new configs
perhaps to name to be more obvious. I'm fine with closing this though as we
have been following the convention that if not documented its not public. It
would just be a convention so easily not followed also.
> annotate the Spark configs to indicate which ones are meant for the end user
> ----------------------------------------------------------------------------
>
> Key: SPARK-3508
> URL: https://issues.apache.org/jira/browse/SPARK-3508
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.1.0
> Reporter: Thomas Graves
>
> Spark has lots of configs floating around. To me configs are like api's and
> we should make it clear which ones are meant for the end user and which ones
> are only used internally. We should decide on exactly how we want to do this.
> I've seen in the past users looking at the code and then using a config that
> was meant to be internal and file a jira to document it. Since there are
> many comitters its easy for someone who doesn't have the history with that
> config to just think we forgot to document it and then it becomes public.
> Perhaps we need to name internal configs specially (spark.internal.) or we
> need to annotate them or something else.
> thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
