[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861928#comment-15861928 ] Hadoop QA commented on SENTRY-1614: --- Here are the results of testing the latest attachm

[jira] [Commented] (SENTRY-1593) Implement client failover for Generic and NN clients

2017-02-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861853#comment-15861853 ] Hadoop QA commented on SENTRY-1593: --- Here are the results of testing the latest attachm

[jira] [Updated] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1614: Attachment: (was: SENTRY-1614.002-sentry-ha-redesign.patch) > DB schema

[jira] [Updated] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1614: Attachment: SENTRY-1614.002-sentry-ha-redesign.patch > DB schema key is too

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861823#comment-15861823 ] Hadoop QA commented on SENTRY-1614: --- Here are the results of testing the latest attachm

[jira] [Updated] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1614: Attachment: SENTRY-1614.002-sentry-ha-redesign.patch > DB schema key is too

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861811#comment-15861811 ] Hadoop QA commented on SENTRY-1614: --- Here are the results of testing the latest attachm

[jira] [Updated] (SENTRY-1614) DB schema key is too long for MySQL

2017-02-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1614: Status: Patch Available (was: In Progress) > DB schema key is too long for

[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients

2017-02-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: SENTRY-1593.003-sentry-ha-redesign.patch > Implement client fai