Hi, @Gokul, we will have to put at least a sample configuration of how a possible proper clustered setup and a pseudo-distributed would be like. So an user can create a setup quickly. And of course, we do not have to put all the possible configuration properties of HBase, for that, pointing to the official HBase documentation is fine. But still, our docs should contain enough information for an user to start with a typical setup. Thank you Nirmal for the comments.
Cheers, Anjana. On Sun, Aug 16, 2015 at 10:20 AM, Nirmal Fernando <[email protected]> wrote: > Also, hbase.master, didn't work of course, that's why I had to read. > > On Sun, Aug 16, 2015 at 10:19 AM, Nirmal Fernando <[email protected]> wrote: > >> Hi Gokul, >> >> I'm sorry, I have to disagree. Here I am talking about a DAS config file, >> not a HBase config file, hence the documentation should be precise and >> clear. >> >> More over, I think you need to test this again. As I read from the >> Internet, hbase.master property is deprecated and clients should use >> Zookeeper quorum IP and Zookeeper client port to retrieve the master >> IP/port, as master ports are allocated dynamically (my setup is a >> pseudo-distributed one). >> >> IMO in our documentation, we should properly guide our users, so they >> don't need to learn it hard-way like I did. >> >> On Sat, Aug 15, 2015 at 11:41 PM, Gokul Balakrishnan <[email protected]> >> wrote: >> >>> Hi Nirmal, >>> >>> The doc that you've pointed merely shows how the datasource should be >>> configured (i.e. the format), and does not necessarily represent a complete >>> configuration, which would naturally depend on the environment. But I agree >>> the wording "add the following configuration" is incorrect and misleading. >>> @Praneesha could you please correct it accordingly? >>> >>> The hbase.master property is used for identifying the HBase master node, >>> through which all schema-related operations would go. So unless the HBase >>> node is in the same machine as the DAS node, that property is required. >>> >>> Thanks, >>> Gokul. >>> >>> >>> On Saturday, 15 August 2015, Nirmal Fernando <[email protected]> wrote: >>> >>>> >>>> https://docs.wso2.com/display/DAS300/Configuring+a+HBase+Datasource >>>> >>>> hbase.master doesn't work, what works is following; >>>> >>>> <datasource> >>>> >>>> <name>WSO2_ANALYTICS_EVENT_STORE_DB_HBASE</name> >>>> >>>> <description>The datasource used for analytics file >>>> system</description> >>>> >>>> <jndiConfig> >>>> >>>> <name>jdbc/WSO2HBaseDB</name> >>>> >>>> </jndiConfig> >>>> >>>> <definition type="HBASE"> >>>> >>>> <configuration> >>>> >>>> *<property>* >>>> >>>> * <name>hbase.zookeeper.quorum</name>* >>>> >>>> * <value>192.168.x.x</value>* >>>> >>>> * </property>* >>>> >>>> <property> >>>> >>>> <name>fs.hdfs.impl</name> >>>> >>>> >>>> <value>org.apache.hadoop.hdfs.DistributedFileSystem</value> >>>> >>>> </property> >>>> >>>> <property> >>>> >>>> <name>fs.file.impl</name> >>>> >>>> >>>> <value>org.apache.hadoop.fs.LocalFileSystem</value> >>>> >>>> </property> >>>> >>>> </configuration> >>>> >>>> </definition> >>>> >>>> </datasource> >>>> >>>> -- >>>> >>>> Thanks & regards, >>>> Nirmal >>>> >>>> Team Lead - WSO2 Machine Learner >>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >>>> Mobile: +94715779733 >>>> Blog: http://nirmalfdo.blogspot.com/ >>>> >>>> >>>> >>> >>> -- >>> Gokul Balakrishnan >>> Senior Software Engineer, >>> WSO2, Inc. http://wso2.com >>> Mob: +94 77 593 5789 | +1 650 272 9927 >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Team Lead - WSO2 Machine Learner >> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> > > > -- > > Thanks & regards, > Nirmal > > Team Lead - WSO2 Machine Learner > Associate Technical Lead - Data Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
