Thanks Josh, Sorry if you felt like I am wasting community time, it took some time for me to figure out how to handle hbase-site.xml for Zeppelin phoenix connection, may be its a zeppelin question than phoenix, in my case the only extra parameter I am using is phoenix.schema.isNamespaceMappingEnabled, I thought it should default to true. thanks for the explanation why it shouldn't
-Sudhir On Thu, Apr 20, 2017 at 11:56 AM, Josh Elser <els...@apache.org> wrote: > Most likely to avoid breaking existing functionality. > > As this mapping is a relatively new feature, we wouldn't want to force it > upon new users. > > The need for Phoenix to have the proper core-site, hdfs-site, and > hbase-site XML files on the classpath is a fair knock though (although, the > lack of ability to provide classpath element continues to boggle my mind as > "normal"). I think discussion around how to better handle this would be a > much better use of your and the community's time :) > > > Sudhir Babu Pothineni wrote: > >> is there any specific reason default value of >> phoenix.schema.isNamespaceMappingEnabled set to false? >> >> when using multiple clients like Zeppelin, DbVisualizer etc.. we need to >> maintain hbase-site.xml. Particularly latest version of Zeppelin is not >> recognizing hbase-site.xml, it worked only when I included into phoenix >> client jar (jar uf phoenix-<version>-client.jar hbase-site.xml). >> >> Thanks >> Sudhir >> >>
