[jira] [Updated] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat updated KUDU-1566: -- Fix Version/s: 1.1.0 > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat resolved KUDU-1566. --- Resolution: Duplicate > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621472#comment-15621472 ] Dinesh Bhat commented on KUDU-1566: --- commit c105fefde20798e9f3671419ca9638a0affea1e5 Author: Dinesh Bhat Date: Tue Oct 25 23:49:29 2016 -0700 [scripts] KUDU-1566: Update jira fields automatically This script is intended to be merged with our existing tools - like pre-push or post-commit, for all commits which start with a JIRA id in their COMMIT_MSG. This helps to track the review patches to JIRA domain and vice versa thereby making it easy to navigate between the two worlds. Currently it comments on the JIRA issue by parsing the commit log for the presence of 'KUDU-[1-9]+' string, and it also updates a review link against 'Code Review' field in jira. Also, it can be leveraged to automatically resolve a JIRA if optional '--resolve=True' is provided. Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat reopened KUDU-1566: --- > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat updated KUDU-1566: -- Comment: was deleted (was: commit c105fefde20798e9f3671419ca9638a0affea1e5 Author: Dinesh Bhat Date: Tue Oct 25 23:49:29 2016 -0700 [scripts] KUDU-1566: Update jira fields automatically This script is intended to be merged with our existing tools - like pre-push or post-commit, for all commits which start with a JIRA id in their COMMIT_MSG. This helps to track the review patches to JIRA domain and vice versa thereby making it easy to navigate between the two worlds. Currently it comments on the JIRA issue by parsing the commit log for the presence of 'KUDU-[1-9]+' string, and it also updates a review link against 'Code Review' field in jira. Also, it can be leveraged to automatically resolve a JIRA if optional '--resolve=True' is provided. Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec ) > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat updated KUDU-1566: -- Comment: was deleted (was: commit c105fefde20798e9f3671419ca9638a0affea1e5 Author: Dinesh Bhat Date: Tue Oct 25 23:49:29 2016 -0700 [scripts] KUDU-1566: Update jira fields automatically This script is intended to be merged with our existing tools - like pre-push or post-commit, for all commits which start with a JIRA id in their COMMIT_MSG. This helps to track the review patches to JIRA domain and vice versa thereby making it easy to navigate between the two worlds. Currently it comments on the JIRA issue by parsing the commit log for the presence of 'KUDU-[1-9]+' string, and it also updates a review link against 'Code Review' field in jira. Also, it can be leveraged to automatically resolve a JIRA if optional '--resolve=True' is provided. Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec ) > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat updated KUDU-1566: -- Comment: was deleted (was: commit c105fefde20798e9f3671419ca9638a0affea1e5 Author: Dinesh Bhat Date: Tue Oct 25 23:49:29 2016 -0700 [scripts] KUDU-1566: Update jira fields automatically This script is intended to be merged with our existing tools - like pre-push or post-commit, for all commits which start with a JIRA id in their COMMIT_MSG. This helps to track the review patches to JIRA domain and vice versa thereby making it easy to navigate between the two worlds. Currently it comments on the JIRA issue by parsing the commit log for the presence of 'KUDU-[1-9]+' string, and it also updates a review link against 'Code Review' field in jira. Also, it can be leveraged to automatically resolve a JIRA if optional '--resolve=True' is provided. Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec ) > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Bhat updated KUDU-1566: -- Comment: was deleted (was: commit c105fefde20798e9f3671419ca9638a0affea1e5 Author: Dinesh Bhat Date: Tue Oct 25 23:49:29 2016 -0700 [scripts] KUDU-1566: Update jira fields automatically This script is intended to be merged with our existing tools - like pre-push or post-commit, for all commits which start with a JIRA id in their COMMIT_MSG. This helps to track the review patches to JIRA domain and vice versa thereby making it easy to navigate between the two worlds. Currently it comments on the JIRA issue by parsing the commit log for the presence of 'KUDU-[1-9]+' string, and it also updates a review link against 'Code Review' field in jira. Also, it can be leveraged to automatically resolve a JIRA if optional '--resolve=True' is provided. Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec ) > JIRA updater script linking a gerrit patch to JIRA automatically > > > Key: KUDU-1566 > URL: https://issues.apache.org/jira/browse/KUDU-1566 > Project: Kudu > Issue Type: Task >Reporter: Dinesh Bhat >Assignee: Dinesh Bhat >Priority: Minor > Fix For: 1.1.0 > > > At times, I have found it hard to track a particular JIRA to a gerrit patch > and vice versa to gain more context on a submitted change, code review > discussions, etc. I am hoping this will bridge the gap between the review > system and JIRA tracking. > Currently, all of our commits do not carry JIRA numbers, but this could be > applicable to whichever gerrit patch carries one in its commit message. I > have come across such scripts before, so spinning one shouldn't be that hard. > Though not as fancy as the below link, we could just add a gerritt link to > JIRA comment section whenever a change is submitted(or perhaps posted for > review). > https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KUDU-1737) Allow KuduContext to create table with column encodings
Jeffrey Shmain created KUDU-1737: Summary: Allow KuduContext to create table with column encodings Key: KUDU-1737 URL: https://issues.apache.org/jira/browse/KUDU-1737 Project: Kudu Issue Type: Improvement Components: api Affects Versions: 1.0.1 Reporter: Jeffrey Shmain Priority: Minor Currently createTable method in KuduContext has no way to specify the column encodings. It uses org.apache.spark.sql.types.StructType, and there seems to be the way to specify optional Metadata in StructField. new StructField(name: String, dataType: DataType, nullable: Boolean = true, metadata: Metadata = Metadata.empty) Can we update the createTable method to parse out optional metadata and add the encodings if specify. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KUDU-1734) Java client timeout exceptions aren't useful
[
https://issues.apache.org/jira/browse/KUDU-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved KUDU-1734.
--
Resolution: Fixed
Assignee: Jean-Daniel Cryans
Fix Version/s: 1.1.0
Target Version/s: 1.1.0
With https://gerrit.cloudera.org/#/c/4871/ I'm going to close this as solved.
Tracing is not in yet but I removed the places where the join() could timeout
before the operation itself gets a timeout. This means that now we'll have more
information, even without full traces.
> Java client timeout exceptions aren't useful
>
>
> Key: KUDU-1734
> URL: https://issues.apache.org/jira/browse/KUDU-1734
> Project: Kudu
> Issue Type: Improvement
> Components: client
>Affects Versions: 1.0.0
>Reporter: Matthew Jacobs
>Assignee: Jean-Daniel Cryans
> Labels: client, impala, usability
> Fix For: 1.1.0
>
>
> When a timeout occurs in the Java client, it throws exceptions that are very
> verbose and hard to make use of.
> For example:
> {code}
> CAUSED BY: NonRecoverableException: Timed out after 1ms when joining
> Deferred@1214130230(state=PENDING, result=null, callback=get tablet locations
> from the master for table Kudu Master -> release master lookup permit ->
> retry RPC -> org.apache.kudu.client.AsyncKuduClient$4@1da21658 -> wakeup
> thread Thread-7, errback=passthrough -> release master lookup permit -> retry
> RPC after error -> passthrough -> wakeup thread Thread-7)
> CAUSED BY: TimeoutException: Timed out after 1ms when joining
> Deferred@1214130230(state=PENDING, result=null, callback=get tablet locations
> from the master for table Kudu Master -> release master lookup permit ->
> retry RPC -> org.apache.kudu.client.AsyncKuduClient$4@1da21658 -> wakeup
> thread Thread-7, errback=passthrough -> release master lookup permit -> retry
> RPC after error -> passthrough -> wakeup thread Thread-7)
> {code}
> Most of the information isn't useful to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KUDU-1618) Add local_replica tool to delete a replica
[ https://issues.apache.org/jira/browse/KUDU-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623066#comment-15623066 ] Dinesh Bhat commented on KUDU-1618: --- Cool, thanks Todd for these ideas, I will spin a patch for that independent of this JIRA. > Add local_replica tool to delete a replica > -- > > Key: KUDU-1618 > URL: https://issues.apache.org/jira/browse/KUDU-1618 > Project: Kudu > Issue Type: Improvement > Components: ops-tooling >Affects Versions: 1.0.0 >Reporter: Todd Lipcon >Assignee: Dinesh Bhat > > Occasionally we've hit cases where a tablet is corrupt in such a way that the > tserver fails to start or crashes soon after starting. Typically we'd prefer > the tablet just get marked FAILED but in the worst case it causes the whole > tserver to fail. > For these cases we should add a 'local_replica' subtool to fully remove a > local tablet. Related, it might be useful to have a 'local_replica archive' > which would create a tarball from the data in this tablet for later > examination by developers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KUDU-1667) Add Python 3 to Jenkins Images
[ https://issues.apache.org/jira/browse/KUDU-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Birdsell reassigned KUDU-1667: - Assignee: Todd Lipcon > Add Python 3 to Jenkins Images > -- > > Key: KUDU-1667 > URL: https://issues.apache.org/jira/browse/KUDU-1667 > Project: Kudu > Issue Type: Bug > Components: build, ops-tooling, python, test >Reporter: Jordan Birdsell >Assignee: Todd Lipcon > Fix For: NA > > > Recently, I've found many regressions or other test failures in Python 3 that > couldve been caught if we also ran python 3 tests on build. We should add > Python 3.5, in addition to python 2, to the Jenkins images used for precommit > tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KUDU-1667) Add Python 3 to Jenkins Images
[ https://issues.apache.org/jira/browse/KUDU-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Birdsell updated KUDU-1667: -- Priority: Minor (was: Major) Issue Type: Test (was: Bug) > Add Python 3 to Jenkins Images > -- > > Key: KUDU-1667 > URL: https://issues.apache.org/jira/browse/KUDU-1667 > Project: Kudu > Issue Type: Test > Components: build, ops-tooling, python, test >Reporter: Jordan Birdsell >Assignee: Todd Lipcon >Priority: Minor > Fix For: NA > > > Recently, I've found many regressions or other test failures in Python 3 that > couldve been caught if we also ran python 3 tests on build. We should add > Python 3.5, in addition to python 2, to the Jenkins images used for precommit > tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
