> All of the Kerberos options already exist in their own legacy locations though - changing their location could break a lot of systems.
We can define the prefix for shared options, and we can strip the prefix when passing these options to the data source. Will this work for your case? On Tue, Sep 25, 2018 at 12:57 PM tigerquoll <tigerqu...@outlook.com> wrote: > I like the shared namespace option better then the white listing option for > any newly defined configuration information. > > All of the Kerberos options already exist in their own legacy locations > though - changing their location could break a lot of systems. > > Perhaps we can use the shared namespace option for any new option and > whitelisting for the existing options? > > > > -- > Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
