Re: Fail to get WEB_CONFIG configurations for data classification

2016-04-08 Thread Zhao Qingwen
I just fixed this bug today, and we can update the configurations on EAGLE
UI directly.

This bug was introduced by a configuration refactor, which only impacts
classification pages, which requires a prefix “web” in front of the
properties.

Later we will update the doc on eagle website.


Best Regards,
Qingwen Zhao | 赵晴雯




2016-04-08 11:48 GMT+08:00 Chen, Hao :

> The bug should be fixed by this PR:
> https://github.com/apache/incubator-eagle/pull/138
>
> From: Edward Zhang mailto:yonzhang2...@gmail.com>>
> Date: Friday, April 8, 2016 at 11:46 AM
> To: "Carnali, Matthew R."  matthew.carn...@capitalone.com>>
> Cc: Qingwen Zhao mailto:qingwz...@ebay.com>>, "Chen,
> Hao" mailto:hao.ch...@ebay.com>>, "Su, Liangfei" <
> li...@ebay.com>
> Subject: Re: Fail to get WEB_CONFIG configurations for data classification
>
> No problem Matt. Please let us know any issues you have run into while you
> are testing.
>
> + more Eagle committers to help.
>
> Thanks
> Edward
>
> On Thu, Apr 7, 2016 at 5:21 PM, Carnali, Matthew R. <
> matthew.carn...@capitalone.com>
> wrote:
> Great thanks will run those first thing tomorrow morning
>
> Sent from my iPhone
>
> On Apr 7, 2016, at 5:12 PM, Edward Zhang  yonzhang2...@gmail.com>> wrote:
>
> Hi Matt,
>
> This is the bug we have introduced in the latest master branch. With this
> bug, we can't use the UI to update site configuration. Could you please try
> the following one of workarounds.
> Workaround 1: run bin/eagle-topology-init.sh
> Wordaround 2: directly run the following 3 curl scripts to populate site
> configurations
>
> echo "Importing applications for sample site ..."
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hdfsAuditLog"}, "enabled": true, "config" :
> "web.fs.defaultFS: \"hdfs://sandbox.hortonworks.com:8020<
> http://sandbox.hortonworks.com:8020>\""}]'
>
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hbaseSecurityLog"}, "enabled": true, "config" :
> "web.hbase.zookeeper.property.clientPort: \"2181\",
> web.hbase.zookeeper.quorum: \"localhost\""}]'
>
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hiveQueryLog"}, "enabled": true,
> "config":"web.accessType:\"metastoredb_jdbc\",web.password:\"hive\",web.user:\"hive\",web.jdbcDriverClassName:\"com.mysql.jdbc.Driver\",web.jdbcUrl:\"jdbc:mysql://
> sandbox.hortonworks.com/hive?createDatabaseIfNotExist=true\<
> http://sandbox.hortonworks.com/hive?createDatabaseIfNotExist=true%5C>""}]'
>
> Please let me know if you can do that.
>
> My skype is hotfeeling_zy, it is also fine we use IM to discuss if you
> like.
>
> @Qingwen, can you file the bug and provide estimated timeline.
>
> Thanks
> Edward
>
> On Thu, Apr 7, 2016 at 4:18 PM, Carnali, Matthew R. <
> matthew.carn...@capitalone.com>
> wrote:
> Hey,
> This is the most recent issue I am seeing.
>
>
>
>
> On 4/6/16, 9:36 AM, "Carnali, Matthew R."  > wrote:
>
> >I am getting the following when I go to Classifications for HDFS:
> >I’ve updated the {"fs.defaultFS":"hdfs://something.com:8020”}
> >
> >But this error now appears.
> >
> >
> >java.lang.Exception: Fail to get WEB_CONFIG configurations for data
> classification
>
> >org.apache.eagle.security.resolver.MetadataAccessConfigRepo.getConfig(MetadataAccessConfigRepo.java:52)
>
> >org.apache.eagle.service.security.hdfs.rest.HDFSResourceWebResource.getHDFSResource(HDFSResourceWebResource.java:64)
> >sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >java.lang.reflect.Method.invoke(Method.java:606)
>
> >com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> >com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>
> >com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> >com.sun.jersey.server.impl.uri.rules.HttpMethodR

Re: Fail to get WEB_CONFIG configurations for data classification

2016-04-08 Thread Zhao Qingwen
I just fixed this bug, and we can update the configurations on EAGLE UI
directly.

This configuration refactor only impacts classification pages, which
requires a prefix “web” in front of the properties.  For other
configurations, it remains the same.

I will update the doc later.


Best Regards,
Qingwen Zhao | 赵晴雯




2016-04-08 11:48 GMT+08:00 Chen, Hao :

> The bug should be fixed by this PR:
> https://github.com/apache/incubator-eagle/pull/138
>
> From: Edward Zhang mailto:yonzhang2...@gmail.com>>
> Date: Friday, April 8, 2016 at 11:46 AM
> To: "Carnali, Matthew R."  matthew.carn...@capitalone.com>>
> Cc: Qingwen Zhao mailto:qingwz...@ebay.com>>, "Chen,
> Hao" mailto:hao.ch...@ebay.com>>, "Su, Liangfei" <
> li...@ebay.com>
> Subject: Re: Fail to get WEB_CONFIG configurations for data classification
>
> No problem Matt. Please let us know any issues you have run into while you
> are testing.
>
> + more Eagle committers to help.
>
> Thanks
> Edward
>
> On Thu, Apr 7, 2016 at 5:21 PM, Carnali, Matthew R. <
> matthew.carn...@capitalone.com>
> wrote:
> Great thanks will run those first thing tomorrow morning
>
> Sent from my iPhone
>
> On Apr 7, 2016, at 5:12 PM, Edward Zhang  yonzhang2...@gmail.com>> wrote:
>
> Hi Matt,
>
> This is the bug we have introduced in the latest master branch. With this
> bug, we can't use the UI to update site configuration. Could you please try
> the following one of workarounds.
> Workaround 1: run bin/eagle-topology-init.sh
> Wordaround 2: directly run the following 3 curl scripts to populate site
> configurations
>
> echo "Importing applications for sample site ..."
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hdfsAuditLog"}, "enabled": true, "config" :
> "web.fs.defaultFS: \"hdfs://sandbox.hortonworks.com:8020<
> http://sandbox.hortonworks.com:8020>\""}]'
>
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hbaseSecurityLog"}, "enabled": true, "config" :
> "web.hbase.zookeeper.property.clientPort: \"2181\",
> web.hbase.zookeeper.quorum: \"localhost\""}]'
>
> curl -u ${EAGLE_SERVICE_USER}:${EAGLE_SERVICE_PASSWD} -X POST -H
> 'Content-Type:application/json' 
> "http://${EAGLE_SERVICE_HOST}:${EAGLE_SERVICE_PORT}/eagle-service/rest/entities?serviceName=SiteApplicationService";
> -d '[{"prefix":"eagleSiteApplication","tags":{"site" : "sandbox",
> "application":"hiveQueryLog"}, "enabled": true,
> "config":"web.accessType:\"metastoredb_jdbc\",web.password:\"hive\",web.user:\"hive\",web.jdbcDriverClassName:\"com.mysql.jdbc.Driver\",web.jdbcUrl:\"jdbc:mysql://
> sandbox.hortonworks.com/hive?createDatabaseIfNotExist=true\<
> http://sandbox.hortonworks.com/hive?createDatabaseIfNotExist=true%5C>""}]'
>
> Please let me know if you can do that.
>
> My skype is hotfeeling_zy, it is also fine we use IM to discuss if you
> like.
>
> @Qingwen, can you file the bug and provide estimated timeline.
>
> Thanks
> Edward
>
> On Thu, Apr 7, 2016 at 4:18 PM, Carnali, Matthew R. <
> matthew.carn...@capitalone.com>
> wrote:
> Hey,
> This is the most recent issue I am seeing.
>
>
>
>
> On 4/6/16, 9:36 AM, "Carnali, Matthew R."  > wrote:
>
> >I am getting the following when I go to Classifications for HDFS:
> >I’ve updated the {"fs.defaultFS":"hdfs://something.com:8020”}
> >
> >But this error now appears.
> >
> >
> >java.lang.Exception: Fail to get WEB_CONFIG configurations for data
> classification
>
> >org.apache.eagle.security.resolver.MetadataAccessConfigRepo.getConfig(MetadataAccessConfigRepo.java:52)
>
> >org.apache.eagle.service.security.hdfs.rest.HDFSResourceWebResource.getHDFSResource(HDFSResourceWebResource.java:64)
> >sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >java.lang.reflect.Method.invoke(Method.java:606)
>
> >com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> >com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>
> >com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> >com.sun.jersey.server.impl.uri.rules.HttpMethodRule.acc

Re: Question Regarding the folder/file name.

2016-04-08 Thread Zhang, Edward (GDI Hadoop)
looks 0.3.0-incubating naming is more informational, like kylin
https://dist.apache.org/repos/dist/release/kylin/

On 4/6/16, 2:49, "Dendukuri, Hemanth"  wrote:
 
>Hi,
>
>I want to upload voted "eagle release candidate 3" artifacts to apache
>release distribution
>https://dist.apache.org/repos/dist/release/incubator/eagle/
>
>Should the name of folder/files contain ³rc3² suffix  or can I rename it
>to just "0.3.0-incubating² and have voted rc3 artifacts in it.
>
>Regards
>Hemanth



Re: Question Regarding the folder/file name.

2016-04-08 Thread Dendukuri, Hemanth
Julian, Please provide your input.  




On 4/8/16, 12:15 PM, "Zhang, Edward (GDI Hadoop)"  wrote:

>looks 0.3.0-incubating naming is more informational, like kylin
>https://dist.apache.org/repos/dist/release/kylin/
>
>On 4/6/16, 2:49, "Dendukuri, Hemanth"  wrote:
> 
>>Hi,
>>
>>I want to upload voted "eagle release candidate 3" artifacts to apache
>>release distribution
>>https://dist.apache.org/repos/dist/release/incubator/eagle/
>>
>>Should the name of folder/files contain ³rc3² suffix  or can I rename it
>>to just "0.3.0-incubating² and have voted rc3 artifacts in it.
>>
>>Regards
>>Hemanth
>


Re: Question Regarding the folder/file name.

2016-04-08 Thread Julian Hyde
Don’t include the release candidate suffix (“-rc3”) in the name of the released 
artifact. Do include ‘-incubating’.

Kylin’s artifacts are good examples to follow: 
https://dist.apache.org/repos/dist/release/kylin/

By the way, I saw that in git you have tag without the ‘-rc3’, namely 
‘release-0.3.0’ tag. This is good. Better would be to have a tag with the same 
name as the release, namely ‘eagle-0.3.0-incubating’. This is what Kylin does.

It’s up to you whether you keep the ‘release-0.3.0-rc3’ tag. I’d be inclined to 
delete it now the release is out. The hash is already on record in the release 
vote.

Julian


> On Apr 8, 2016, at 1:47 PM, Dendukuri, Hemanth  wrote:
> 
> Julian, Please provide your input.  
> 
> 
> 
> 
> On 4/8/16, 12:15 PM, "Zhang, Edward (GDI Hadoop)"  wrote:
> 
>> looks 0.3.0-incubating naming is more informational, like kylin
>> https://dist.apache.org/repos/dist/release/kylin/
>> 
>> On 4/6/16, 2:49, "Dendukuri, Hemanth"  wrote:
>> 
>>> Hi,
>>> 
>>> I want to upload voted "eagle release candidate 3" artifacts to apache
>>> release distribution
>>> https://dist.apache.org/repos/dist/release/incubator/eagle/
>>> 
>>> Should the name of folder/files contain ³rc3² suffix  or can I rename it
>>> to just "0.3.0-incubating² and have voted rc3 artifacts in it.
>>> 
>>> Regards
>>> Hemanth
>> 



Re: Question Regarding the folder/file name.

2016-04-08 Thread Dendukuri, Hemanth
Thanks Julian, 
 
Sure I will update the tag name to "eagle-0.3.0-incubating” and also push 
artifacts without suffix (“-rc3”). 



On 4/8/16, 3:53 PM, "Julian Hyde"  wrote:

>Don’t include the release candidate suffix (“-rc3”) in the name of the 
>released artifact. Do include ‘-incubating’.
>
>Kylin’s artifacts are good examples to follow: 
>https://dist.apache.org/repos/dist/release/kylin/
>
>By the way, I saw that in git you have tag without the ‘-rc3’, namely 
>‘release-0.3.0’ tag. This is good. Better would be to have a tag with the same 
>name as the release, namely ‘eagle-0.3.0-incubating’. This is what Kylin does.
>
>It’s up to you whether you keep the ‘release-0.3.0-rc3’ tag. I’d be inclined 
>to delete it now the release is out. The hash is already on record in the 
>release vote.
>
>Julian
>
>
>> On Apr 8, 2016, at 1:47 PM, Dendukuri, Hemanth  wrote:
>> 
>> Julian, Please provide your input.  
>> 
>> 
>> 
>> 
>> On 4/8/16, 12:15 PM, "Zhang, Edward (GDI Hadoop)"  wrote:
>> 
>>> looks 0.3.0-incubating naming is more informational, like kylin
>>> https://dist.apache.org/repos/dist/release/kylin/
>>> 
>>> On 4/6/16, 2:49, "Dendukuri, Hemanth"  wrote:
>>> 
 Hi,
 
 I want to upload voted "eagle release candidate 3" artifacts to apache
 release distribution
 https://dist.apache.org/repos/dist/release/incubator/eagle/
 
 Should the name of folder/files contain ³rc3² suffix  or can I rename it
 to just "0.3.0-incubating² and have voted rc3 artifacts in it.
 
 Regards
 Hemanth
>>> 
>