[jira] [Commented] (EAGLE-201) Change maven group name to org.apache.eagle instead of eagle

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-201:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/125


> Change maven group name to org.apache.eagle instead of eagle
> 
>
> Key: EAGLE-201
> URL: https://issues.apache.org/jira/browse/EAGLE-201
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[jira] [Commented] (EAGLE-201) Change maven group name to org.apache.eagle instead of eagle

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-201:
--

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/125

EAGLE-201 Change maven group id to "org.apache.eagle" instead of "eagle"

https://issues.apache.org/jira/browse/EAGLE-201

EAGLE-201 Change maven group id to "org.apache.eagle" instead of "eagle"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle EAGLE-201

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/125.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #125


commit beae6d2f24d8622c26dd1a0a34db3f5962f60342
Author: Hao Chen 
Date:   2016-03-15T02:02:34Z

EAGLE-201




> Change maven group name to org.apache.eagle instead of eagle
> 
>
> Key: EAGLE-201
> URL: https://issues.apache.org/jira/browse/EAGLE-201
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: EAGLE-201 Change maven group id to "...

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/125

EAGLE-201 Change maven group id to "org.apache.eagle" instead of "eagle"

https://issues.apache.org/jira/browse/EAGLE-201

EAGLE-201 Change maven group id to "org.apache.eagle" instead of "eagle"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle EAGLE-201

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/125.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #125


commit beae6d2f24d8622c26dd1a0a34db3f5962f60342
Author: Hao Chen 
Date:   2016-03-15T02:02:34Z

EAGLE-201




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-201) Change maven group name to org.apache.eagle instead of eagle

[Hao Chen (JIRA)]

Hao Chen created EAGLE-201:
--

 Summary: Change maven group name to org.apache.eagle instead of 
eagle
 Key: EAGLE-201
 URL: https://issues.apache.org/jira/browse/EAGLE-201
 Project: Eagle
  Issue Type: Improvement
Reporter: Hao Chen
Assignee: Hao Chen






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

[jira] [Resolved] (EAGLE-200) GC Log Monitoring Not Working

[Senthilkumar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Senthilkumar resolved EAGLE-200.

Resolution: Done

> GC Log Monitoring  Not Working
> --
>
> Key: EAGLE-200
> URL: https://issues.apache.org/jira/browse/EAGLE-200
> Project: Eagle
>  Issue Type: Bug
> Environment: Production
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>
> GCLog Analyzer throws below Exception.
> 2016-03-14T11:28:13.527+ o.a.e.d.s.JsonMessageDeserializer [ERROR] Failed 
> to deserialize json from: 2014-08-13T12:22:25.488-0700: 144.526: [Full 
> GC2014-08-13T12:22:25.488-0700: 144.526: [CMS: 
> 9845647K->10115891K(97517568K), 14.2064400 secs] 
> 10215536K->10115891K(100348736K), [CMS Perm : 24119K->24107K(24320K)], 
> 14.2066090 secs] [Times: user=13.86 sys=0.32, real=14.20 secs]
> com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize 
> instance of java.util.TreeMap out of VALUE_NUMBER_INT token
>  at [Source: [B@2018d6d4; line: 1, column: 1]
> at 
> com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:164)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:575)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:569)
>  ~[stormjar.jar:na]



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

[jira] [Commented] (EAGLE-200) GC Log Monitoring Not Working

[Senthilkumar (JIRA)]

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

Senthilkumar commented on EAGLE-200:


Modified Config .. Will test with changes tomorrow.. 


> GC Log Monitoring  Not Working
> --
>
> Key: EAGLE-200
> URL: https://issues.apache.org/jira/browse/EAGLE-200
> Project: Eagle
>  Issue Type: Bug
> Environment: Production
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>
> GCLog Analyzer throws below Exception.
> 2016-03-14T11:28:13.527+ o.a.e.d.s.JsonMessageDeserializer [ERROR] Failed 
> to deserialize json from: 2014-08-13T12:22:25.488-0700: 144.526: [Full 
> GC2014-08-13T12:22:25.488-0700: 144.526: [CMS: 
> 9845647K->10115891K(97517568K), 14.2064400 secs] 
> 10215536K->10115891K(100348736K), [CMS Perm : 24119K->24107K(24320K)], 
> 14.2066090 secs] [Times: user=13.86 sys=0.32, real=14.20 secs]
> com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize 
> instance of java.util.TreeMap out of VALUE_NUMBER_INT token
>  at [Source: [B@2018d6d4; line: 1, column: 1]
> at 
> com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:164)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:575)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:569)
>  ~[stormjar.jar:na]



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

[GitHub] incubator-eagle pull request: Eagle 198 integrate new Siddhi versi...

[yonzhang]

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/122#issuecomment-196411766
  
now after 3.0.5, the default exception handler is not 
FatalExceptionHandler, do we still need SiddhiPolicyExceptionHandler?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-200) GC Log Monitoring Not Working

[Su Ralph (JIRA)]

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

Su Ralph commented on EAGLE-200:


The GC log inputs are text log lines and not expected to be JSON string, while 
the given errror show JSON deserializer is used.

> GC Log Monitoring  Not Working
> --
>
> Key: EAGLE-200
> URL: https://issues.apache.org/jira/browse/EAGLE-200
> Project: Eagle
>  Issue Type: Bug
> Environment: Production
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>
> GCLog Analyzer throws below Exception.
> 2016-03-14T11:28:13.527+ o.a.e.d.s.JsonMessageDeserializer [ERROR] Failed 
> to deserialize json from: 2014-08-13T12:22:25.488-0700: 144.526: [Full 
> GC2014-08-13T12:22:25.488-0700: 144.526: [CMS: 
> 9845647K->10115891K(97517568K), 14.2064400 secs] 
> 10215536K->10115891K(100348736K), [CMS Perm : 24119K->24107K(24320K)], 
> 14.2066090 secs] [Times: user=13.86 sys=0.32, real=14.20 secs]
> com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize 
> instance of java.util.TreeMap out of VALUE_NUMBER_INT token
>  at [Source: [B@2018d6d4; line: 1, column: 1]
> at 
> com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:164)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:575)
>  ~[stormjar.jar:na]
> at 
> com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:569)
>  ~[stormjar.jar:na]



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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #54

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-main (build #54) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/54/ to view the results. 
Test Report is at: Test Result

[GitHub] incubator-eagle pull request: EAGLE-191 Fix Copyright message and ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/115


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-191) Fix Copyright message and update pom version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-191:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/115


> Fix Copyright message and update pom version
> 
>
> Key: EAGLE-191
> URL: https://issues.apache.org/jira/browse/EAGLE-191
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>




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

[GitHub] incubator-eagle pull request: EAGLE-191 Fix Copyright message and ...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/115#issuecomment-196243312
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: Update dependency license file

[haoch]

Github user haoch closed the pull request at:

https://github.com/apache/incubator-eagle/pull/124


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: Update dependency license file

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/124

Update dependency license file



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle 
update-dependency-license

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/124.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #124


commit 986a9996f9d9e80f53f841bbfe61cffab566eacf
Author: Hao Chen 
Date:   2016-03-14T08:35:32Z

Update dependency license file




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-199) gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-199:
--

Github user haoch closed the pull request at:

https://github.com/apache/incubator-eagle/pull/123


> gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz 
> avoiding binary file in source code
> -
>
> Key: EAGLE-199
> URL: https://issues.apache.org/jira/browse/EAGLE-199
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: EAGLE-199 gzip lib/EAGLE/package/pat...

[haoch]

Github user haoch closed the pull request at:

https://github.com/apache/incubator-eagle/pull/123


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-199) gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code

[Hao Chen (JIRA)]

Hao Chen created EAGLE-199:
--

 Summary: gzip lib/EAGLE/package/patches/app.js 
lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code
 Key: EAGLE-199
 URL: https://issues.apache.org/jira/browse/EAGLE-199
 Project: Eagle
  Issue Type: New Feature
Reporter: Hao Chen
Assignee: Hao Chen






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

[jira] [Commented] (EAGLE-199) gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-199:
--

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/123

EAGLE-199 gzip lib/EAGLE/package/patches/app.js 
lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code

https://issues.apache.org/jira/browse/EAGLE-199

gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz 
avoiding binary file in source code

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle fix-app.js.gz

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #123


commit d2921276d80a4acd45b222cdb6fb50234d577418
Author: Hao Chen 
Date:   2016-03-14T06:13:47Z

Merge branch 'module' of https://github.com/zombieJ/incubator-eagle into 
module

Conflicts:
eagle-assembly/src/main/bin/eagle-env.sh

eagle-security/eagle-security-hdfs-web/src/main/java/org/apache/eagle/service/security/hdfs/HDFSResourceUtils.java

eagle-security/eagle-security-hive-web/src/main/java/org/apache/eagle/service/security/hive/dao/HiveMetadataAccessConfigDAOImpl.java
eagle-webservice/src/main/webapp/Gruntfile.js
eagle-webservice/src/main/webapp/app/index.html
eagle-webservice/src/main/webapp/app/partials/dam/sensitivity.html

eagle-webservice/src/main/webapp/app/partials/dam/sensitivitySummary.html
eagle-webservice/src/main/webapp/app/partials/dam/streamList.html
eagle-webservice/src/main/webapp/app/partials/dam/summary.html
eagle-webservice/src/main/webapp/app/public/css/main.css

eagle-webservice/src/main/webapp/app/public/feature/classification/controller.js

eagle-webservice/src/main/webapp/app/public/feature/classification/page/sensitivity.html
eagle-webservice/src/main/webapp/app/public/feature/common/controller.js

eagle-webservice/src/main/webapp/app/public/feature/common/page/alertList.html

eagle-webservice/src/main/webapp/app/public/feature/common/page/policyList.html

eagle-webservice/src/main/webapp/app/public/feature/metadata/controller.js

eagle-webservice/src/main/webapp/app/public/feature/metadata/page/streamList.html

eagle-webservice/src/main/webapp/app/public/feature/userProfile/controller.js

eagle-webservice/src/main/webapp/app/public/feature/userProfile/page/detail.html
eagle-webservice/src/main/webapp/app/public/js/app.js

eagle-webservice/src/main/webapp/app/public/js/ctrl/configurationController.js
eagle-webservice/src/main/webapp/app/public/js/ctrl/main.js
eagle-webservice/src/main/webapp/app/public/js/srv/applicationSrv.js
eagle-webservice/src/main/webapp/app/public/js/srv/entitiesSrv.js
eagle-webservice/src/main/webapp/app/public/js/srv/uiSrv.js




> gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz 
> avoiding binary file in source code
> -
>
> Key: EAGLE-199
> URL: https://issues.apache.org/jira/browse/EAGLE-199
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request: EAGLE-199 gzip lib/EAGLE/package/pat...

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/123

EAGLE-199 gzip lib/EAGLE/package/patches/app.js 
lib/EAGLE/package/patches/app.js.gz avoiding binary file in source code

https://issues.apache.org/jira/browse/EAGLE-199

gzip lib/EAGLE/package/patches/app.js lib/EAGLE/package/patches/app.js.gz 
avoiding binary file in source code

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle fix-app.js.gz

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #123


commit d2921276d80a4acd45b222cdb6fb50234d577418
Author: Hao Chen 
Date:   2016-03-14T06:13:47Z

Merge branch 'module' of https://github.com/zombieJ/incubator-eagle into 
module

Conflicts:
eagle-assembly/src/main/bin/eagle-env.sh

eagle-security/eagle-security-hdfs-web/src/main/java/org/apache/eagle/service/security/hdfs/HDFSResourceUtils.java

eagle-security/eagle-security-hive-web/src/main/java/org/apache/eagle/service/security/hive/dao/HiveMetadataAccessConfigDAOImpl.java
eagle-webservice/src/main/webapp/Gruntfile.js
eagle-webservice/src/main/webapp/app/index.html
eagle-webservice/src/main/webapp/app/partials/dam/sensitivity.html

eagle-webservice/src/main/webapp/app/partials/dam/sensitivitySummary.html
eagle-webservice/src/main/webapp/app/partials/dam/streamList.html
eagle-webservice/src/main/webapp/app/partials/dam/summary.html
eagle-webservice/src/main/webapp/app/public/css/main.css

eagle-webservice/src/main/webapp/app/public/feature/classification/controller.js

eagle-webservice/src/main/webapp/app/public/feature/classification/page/sensitivity.html
eagle-webservice/src/main/webapp/app/public/feature/common/controller.js

eagle-webservice/src/main/webapp/app/public/feature/common/page/alertList.html

eagle-webservice/src/main/webapp/app/public/feature/common/page/policyList.html

eagle-webservice/src/main/webapp/app/public/feature/metadata/controller.js

eagle-webservice/src/main/webapp/app/public/feature/metadata/page/streamList.html

eagle-webservice/src/main/webapp/app/public/feature/userProfile/controller.js

eagle-webservice/src/main/webapp/app/public/feature/userProfile/page/detail.html
eagle-webservice/src/main/webapp/app/public/js/app.js

eagle-webservice/src/main/webapp/app/public/js/ctrl/configurationController.js
eagle-webservice/src/main/webapp/app/public/js/ctrl/main.js
eagle-webservice/src/main/webapp/app/public/js/srv/applicationSrv.js
eagle-webservice/src/main/webapp/app/public/js/srv/entitiesSrv.js
eagle-webservice/src/main/webapp/app/public/js/srv/uiSrv.js




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-190:
---
Affects Version/s: v0.3.0

> JBDC Metadata Storage Extension
> ---
>
> Key: EAGLE-190
> URL: https://issues.apache.org/jira/browse/EAGLE-190
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> JDBC as metadata storage maybe more convenient and light-weight for user to 
> use.
> * Support Derby in Memory: The JDBC can support derby and mysql completely, 
> and use derby in memory by default, so that user don’t have to install any 
> additional dependencies even mysql to get started, and also our unit test 
> could easily pass without any tricky modifications.
> * Automatic DDL Schema Manager: JdbcEntitySchemaManager could automatically 
> create all required tables if not existing when application is started.
> * Fixed JDBC reserved field name like desc, group and so on
> * Force update while inserting failed due to duplicated key exception



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

[GitHub] incubator-eagle pull request: EAGLE-190 JBDC Metadata Storage Exte...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/118#issuecomment-196157852
  
I think the PR is ready enough to be merged into master branch, please help 
review @yonzhang 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Hao Chen (JIRA)]

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

Hao Chen updated EAGLE-190:
---
Description: 
JDBC as metadata storage maybe more convenient and light-weight for user to use.

* Support Derby in Memory: The JDBC can support derby and mysql completely, and 
use derby in memory by default, so that user don’t have to install any 
additional dependencies even mysql to get started, and also our unit test could 
easily pass without any tricky modifications.
* Automatic DDL Schema Manager: JdbcEntitySchemaManager could automatically 
create all required tables if not existing when application is started.
* Fixed JDBC reserved field name like desc, group and so on
* Force update while inserting failed due to duplicated key exception

  was:JDBC as metadata storage maybe more convenient and light-weight for user 
to use.


> 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.
> * Support Derby in Memory: The JDBC can support derby and mysql completely, 
> and use derby in memory by default, so that user don’t have to install any 
> additional dependencies even mysql to get started, and also our unit test 
> could easily pass without any tricky modifications.
> * Automatic DDL Schema Manager: JdbcEntitySchemaManager could automatically 
> create all required tables if not existing when application is started.
> * Fixed JDBC reserved field name like desc, group and so on
> * Force update while inserting failed due to duplicated key exception



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