RE: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Jaspaul Chahal
Hi Ed,

Thanks, I am using 0.4 .  The connection is successful using ? and then 
connection parameters. 

Will try more connection parameters those I wanted to try and will keep you 
posted in case I find any issue.

Thanks again!

Regards,
Jaspaul Chahal

-Original Message-
From: Edward Zhang [mailto:yonzhang2...@apache.org] 
Sent: Wednesday, September 21, 2016 11:38 AM
To: dev@eagle.incubator.apache.org
Cc: Subra Ramesh <sram...@dataguise.com>
Subject: Re: MySql Connection properties in eagle-service.conf

In order not to block your current work, maybe you can try to config 
storage-connection-url to append extra connection properties, for example the 
following

url="jdbc:mysql://localhost/eagle_db?useUnicode=yescharacterEncoding=utf8"


On Wed, Sep 21, 2016 at 11:26 AM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> This connection-props is not applied in the code, but it should be 
> appended to end of connection string. I am looking into the place 
> where we can hook this configuration. Are you using Eagle 0.3?
>
> Thanks
> Edward
>
> On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal 
> <jasp...@dataguise.com>
> wrote:
>
>> Anyone from Apache Eagle team please?
>>
>> Regards,
>> Jaspaul
>>
>> From: Jaspaul Chahal
>> Sent: Tuesday, September 20, 2016 5:26 PM
>> To: dev@eagle.incubator.apache.org
>> Cc: Subra Ramesh (sram...@dataguise.com) <sram...@dataguise.com>
>> Subject: MySql Connection properties in eagle-service.conf
>>
>> Hello Team,
>>
>> It's regarding MySql as backend repo fro Apache Eagle.
>>
>> In eagle-service.conf file for MySql we have the following property:
>>storage-connection-props="encoding=UTF-8"
>>
>> But, I couldn't find the code using this property for the connection 
>> creation in  
>> TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
>> config) .
>>
>> Can someone please point me to the code where we are using this 
>> connection properties for the connection. I need to pass some extra 
>> connection parameters for MySql.
>>
>> Thanks in advance!
>>
>> Regards,
>> Jaspaul Chahal
>>
>
>


RE: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Jaspaul Chahal
Anyone from Apache Eagle team please?

Regards,
Jaspaul

From: Jaspaul Chahal
Sent: Tuesday, September 20, 2016 5:26 PM
To: dev@eagle.incubator.apache.org
Cc: Subra Ramesh (sram...@dataguise.com) <sram...@dataguise.com>
Subject: MySql Connection properties in eagle-service.conf

Hello Team,

It's regarding MySql as backend repo fro Apache Eagle.

In eagle-service.conf file for MySql we have the following property:
   storage-connection-props="encoding=UTF-8"

But, I couldn't find the code using this property for the connection creation 
in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig config) .

Can someone please point me to the code where we are using this connection 
properties for the connection. I need to pass some extra connection parameters 
for MySql.

Thanks in advance!

Regards,
Jaspaul Chahal


MySql Connection properties in eagle-service.conf

2016-09-20 Thread Jaspaul Chahal
Hello Team,

It's regarding MySql as backend repo fro Apache Eagle.

In eagle-service.conf file for MySql we have the following property:
   storage-connection-props="encoding=UTF-8"

But, I couldn't find the code using this property for the connection creation 
in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig config) .

Can someone please point me to the code where we are using this connection 
properties for the connection. I need to pass some extra connection parameters 
for MySql.

Thanks in advance!

Regards,
Jaspaul Chahal


RE: Eagle credentials

2016-05-23 Thread Jaspaul Chahal

Thanks Huizhi, I will try this out and will get back to you, if have more 
questions.

Regards,
Jaspaul 

-Original Message-
From: Huizhi Lu [mailto:ihuizhi...@gmail.com] 
Sent: Monday, May 23, 2016 2:16 PM
To: dev@eagle.incubator.apache.org
Cc: Subra Ramesh <sram...@dataguise.com>
Subject: Re: Eagle credentials

Hi Jaspaul,

We support 2 types of credential verification:

1) We use javax.xml.bind.DatatypeConverter Base64  to encode encrypted 
authentication. This is used for testing/sandbox.
And please note that authority is also used -- ROLE_USER, ROLE_ADMIN.

The information is in the following file. We can set it up in the following 
file. It means you can change the username/password in the following 
configuration. You need to use Base64 to encode your password and replace the 
following password's value.

eagle/lib/tomcat/webapps/eagle-service/WEB-INF/classes/eagleSecurity.xml

  Please note that this is NOT recommended. It might 
be hacked and password may be leaked.

2) LDAP is supported and recommended. We can enable LDAP this way:
a) Edit conf/eagle-service.conf. change springActiveProfile="default"
b) Edit conf/ldap.properties 

If you still have any questions, please feel free to contact us. Thanks.

-Huizhi


> On May 23, 2016, at 11:06 AM, Jaspaul Chahal <jasp...@dataguise.com> wrote:
> 
> Hello,
> 
> This is related to Apache Eagle credentials, we know that the default 
> credentials are admin/secret.
> But, I want to change the credentials to something else. Only place, I know, 
> where we specify the credentials are in "~ /eagle/bin/eagle-env.sh" file . 
> Even if I change the EAGLE_SERVICE_USER and EAGLE_SERVICE_PASSWD and restart 
> Apache Eagle service, it doesn't reflect the change.
> 
> Can you please guide me, how can I change the credentials for Apache Eagle 
> service?
> 
> 
> Thanks and regards,
> Jaspaul Chahal



RE: SMTP settings for Email alerts

2016-05-12 Thread Jaspaul Chahal
Thanks Huizhi,

Great! that's exactly what I was looking for, I wanted to use TLS .

-Jaspaul

-Original Message-
From: Huizhi Lu [mailto:ihuizhi...@gmail.com] 
Sent: Thursday, May 12, 2016 10:06 AM
To: dev@eagle.incubator.apache.org
Subject: Re: SMTP settings for Email alerts

Hi Jaspaul,

I have fixed the bugs in a pull request but it has not been merged into master.
We can set the email in application conf like the following.
"mailHost" : "smtp.office365.com",
"mailSmtpPort":"587",
"mailSmtpAuth" : "true",
"mailSmtpUser" : "username",
"mailSmtpPassword" : "password",
#"mailSmtpSslEnable" : "true",
"mailSmtpTlsEnable" : "true",

-Huizhi

> On May 10, 2016, at 10:27 PM, Zhang, Edward (GDI Hadoop) <yonzh...@ebay.com> 
> wrote:
> 
> You can pass auth configuration through configuration, by default this 
> is disabled.Please try it.
> 
> mail.smtp.auth=true
> 
> mail.user
> 
> mail.pwd
> 
> 
> 
> But I do see there is possibly a bug with this, in AlertEmailSender, 
> those Auth information is not passed into EagleMailClient.
> 
> Thanks
> Edward
> 
> On 5/10/16, 12:02, "Jaspaul Chahal" <jasp...@dataguise.com> wrote:
> 
>> Hi Guys,
>> 
>> I am looking for SMTP settings for email alerts in Apache Eagle.  I 
>> see the following properties in conf files:
>> 
>> "mailHost" : "mailHost.com",
>> "mailSmtpPort":"25",
>> "mailDebug" : "true"
>> 
>> The question is don't we need user/pass for SMTP server authentication?
>> how to pass that info?
>> 
>> Thanks in Advance!
>> 
>> Jaspaul Chahal
> 



SMTP settings for Email alerts

2016-05-10 Thread Jaspaul Chahal
Hi Guys,

I am looking for SMTP settings for email alerts in Apache Eagle.  I see the 
following properties in conf files:

"mailHost" : "mailHost.com",
"mailSmtpPort":"25",
"mailDebug" : "true"

The question is don't we need user/pass for SMTP server authentication? how to 
pass that info?

Thanks in Advance!

Jaspaul Chahal


[jira] [Commented] (EAGLE-291) JDBC: Update transactions fail in PostgreSQL

2016-05-03 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269707#comment-15269707
 ] 

Jaspaul Chahal commented on EAGLE-291:
--

PR opened for this issue : https://github.com/apache/incubator-eagle/pull/174
Used save-point to get rid of previous failed insert entity transaction and 
then continue with update transaction.

> JDBC: Update transactions fail in PostgreSQL
> 
>
> Key: EAGLE-291
> URL: https://issues.apache.org/jira/browse/EAGLE-291
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
> Environment: Linux, PostgreSQL 9.1  as metadata store.
>    Reporter: Jaspaul Chahal
> Fix For: v0.4.0
>
>
> When it tries to update some entity, throws the following exception: 
> org.apache.torque.TorqueException: org.postgresql.util.PSQLException: ERROR: 
> current transaction is aborted, commands ignored until end of transaction 
> block.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (EAGLE-270) JDBC: Create table fail for some of the tables

2016-04-18 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246136#comment-15246136
 ] 

Jaspaul Chahal commented on EAGLE-270:
--

I can fix this issue. will issue PR for this.

> JDBC: Create table fail for some of the tables
> --
>
> Key: EAGLE-270
> URL: https://issues.apache.org/jira/browse/EAGLE-270
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.1
> Environment: MySql as backend metadata store
>    Reporter: Jaspaul Chahal
> Fix For: v0.4.0
>
>
> There are total 24 tables in schema. But only 14 are created automatically 
> and rest of the tables are not created due to the following error:
> "Row size too large error (65535)" .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-270) JDBC: Create table fail for some of the tables

2016-04-18 Thread Jaspaul Chahal (JIRA)
Jaspaul Chahal created EAGLE-270:


 Summary: JDBC: Create table fail for some of the tables
 Key: EAGLE-270
 URL: https://issues.apache.org/jira/browse/EAGLE-270
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.3.1
 Environment: MySql as backend metadata store
Reporter: Jaspaul Chahal
 Fix For: v0.4.0


There are total 24 tables in schema. But only 14 are created automatically and 
rest of the tables are not created due to the following error:

"Row size too large error (65535)" .





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (EAGLE-190) JBDC Metadata Storage Extension

2016-03-08 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186212#comment-15186212
 ] 

Jaspaul Chahal edited comment on EAGLE-190 at 3/9/16 1:04 AM:
--

When I was looking into it, I concluded that we need to registerJdbcType for 
double[]. Not sure if Types.ARRAY will do the job or need changes in code for 
that. Serializing the array before saving can be the other option.


was (Author: jashchahal):
When I was looking into it, I concluded that we need to registerJdbcType for 
double[]. Not sure if Types.ARRAY will do the job or need changes in code for 
that.

> JBDC Metadata Storage Extension
> ---
>
> Key: EAGLE-190
> URL: https://issues.apache.org/jira/browse/EAGLE-190
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> JDBC as metadata storage maybe more convenient and light-weight for user to 
> use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (EAGLE-190) JBDC Metadata Storage Extension

2016-03-08 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186212#comment-15186212
 ] 

Jaspaul Chahal commented on EAGLE-190:
--

When I was looking into it, I concluded that we need to registerJdbcType for 
double[]. Not sure if Types.ARRAY will do the job or need changes in code for 
that.

> JBDC Metadata Storage Extension
> ---
>
> Key: EAGLE-190
> URL: https://issues.apache.org/jira/browse/EAGLE-190
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> JDBC as metadata storage maybe more convenient and light-weight for user to 
> use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Eagle 0.3 with Mysql

2016-02-18 Thread Jaspaul Chahal
Hi,


I am trying to get Eagle 0.3 (cloned yesterday) working with MySql as 
storage-type. I have created the tables mentioned at 
https://cwiki.apache.org/confluence/display/EAG/JDBC+Extension and also have 
put the eagle-storage-jdbc-0.3.0.jar in lib of Eagle service. It complained 
"java.lang.NoClassDefFoundError: org/apache/torque/TorqueException", so I have 
put torque-runtime-4.0.jar to lib and this error is gone.


Now, it is complaining "Table 'eagle.ipzone_ipzone' doesn't exist" while 
executing 'SELECT ipzone_ipzone.* FROM ipzone_ipzone WHERE 
(ipzone_ipzone.timestamp>=? AND ipzone_ipzone.timestamp

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

2016-02-18 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152961#comment-15152961
 ] 

Jaspaul Chahal commented on EAGLE-127:
--

If try to build Eagle, where we don't have git installed, it fails. Why do we 
need git for build?

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Prasad Mujumdar
>Priority: Trivial
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

2016-02-18 Thread Jaspaul Chahal (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152843#comment-15152843
 ] 

Jaspaul Chahal commented on EAGLE-127:
--

yes, I didn't realize it failed due to NPM, I had to go thru the documentation 
again.

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Prasad Mujumdar
>Priority: Trivial
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)