[jira] [Updated] (DRILL-6230) Extend row set readers to handle hyper vectors
[ https://issues.apache.org/jira/browse/DRILL-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-6230: --- Description: The current row set readers have incomplete support for hyper-vectors. To add full support, we need an interface that supports either single batches or hyper batches. Accessing vectors in hyper batches differs depending on whether the vector is at the top level or is nested. See [this post|https://github.com/paul-rogers/drill/wiki/BH-Column-Readers] for details. Also includes a simpler reader template: replaces the original three classes with one, in parallel with the writers. (was: The current row set readers have incomplete support for hyper-vectors. To add full support, we need an interface that supports either single batches or hyper batches. Accessing vectors in hyper batches differs depending on whether the vector is at the top level or is nested. See [this post|https://github.com/paul-rogers/drill/wiki/BH-Column-Readers] for details.) > Extend row set readers to handle hyper vectors > -- > > Key: DRILL-6230 > URL: https://issues.apache.org/jira/browse/DRILL-6230 > Project: Apache Drill > Issue Type: Improvement >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Major > Fix For: 1.14.0 > > > The current row set readers have incomplete support for hyper-vectors. To add > full support, we need an interface that supports either single batches or > hyper batches. Accessing vectors in hyper batches differs depending on > whether the vector is at the top level or is nested. See [this > post|https://github.com/paul-rogers/drill/wiki/BH-Column-Readers] for > details. Also includes a simpler reader template: replaces the original three > classes with one, in parallel with the writers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6230) Extend row set readers to handle hyper vectors
Paul Rogers created DRILL-6230: -- Summary: Extend row set readers to handle hyper vectors Key: DRILL-6230 URL: https://issues.apache.org/jira/browse/DRILL-6230 Project: Apache Drill Issue Type: Improvement Reporter: Paul Rogers Assignee: Paul Rogers Fix For: 1.14.0 The current row set readers have incomplete support for hyper-vectors. To add full support, we need an interface that supports either single batches or hyper batches. Accessing vectors in hyper batches differs depending on whether the vector is at the top level or is nested. See [this post|https://github.com/paul-rogers/drill/wiki/BH-Column-Readers] for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly
[
https://issues.apache.org/jira/browse/DRILL-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394229#comment-16394229
]
ASF GitHub Bot commented on DRILL-6217:
---
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/1154
> NaN/Inf: NestedLoopJoin processes NaN values incorrectly
>
>
> Key: DRILL-6217
> URL: https://issues.apache.org/jira/browse/DRILL-6217
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.12.0
>Reporter: Volodymyr Tkach
>Assignee: Volodymyr Tkach
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.13.0
>
> Attachments: ObjsX.json
>
>
> *AFFECTED_FUNCTIONALITY:* INNER JOIN (nestedloopjoin)
> *ISSUE_DESCRIPTION:* according to *nestedloopjoin* query result NaN != NaN,
> however hashjoin / mergejoin behaves another way - NaN = NaN. As far as I
> understand, nestedloopjoin should behave like hashjoin / mergejoin. *STEPS*:
> - Upload the attached file to Hadoop fs (ObjsX.json);
> - Setup the following system settings:
> *set planner.enable_nljoin_for_scalar_only = false*
> *set planner.enable_hashjoin = false*
> *set planner.enable_mergejoin = false*
> *set planner.enable_nestedloopjoin = true*
> - Run the following sql query {code} select distinct t.name from
> dfs.tmp.`ObjsX.json` t inner join dfs.tmp.`ObjsX.json` tt on t.attr4 =
> tt.attr4 {code}
> *EXPECTED_RESULT:* It was expected to get the following result:
> {code}
>object1
>object2
>object3
>object4
> {code}
>
> *ACTUAL_RESULT:* The actual result is:
> {code}
>object2
>object3
>object4
> {code}
> Please investigate and fix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6213) During restart drillbit should be killed forcefully if exceeds allowed timeout
[ https://issues.apache.org/jira/browse/DRILL-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394227#comment-16394227 ] ASF GitHub Bot commented on DRILL-6213: --- Github user asfgit closed the pull request at: https://github.com/apache/drill/pull/1155 > During restart drillbit should be killed forcefully if exceeds allowed timeout > -- > > Key: DRILL-6213 > URL: https://issues.apache.org/jira/browse/DRILL-6213 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.12.0 >Reporter: Arina Ielchiieva >Assignee: Arina Ielchiieva >Priority: Major > Labels: ready-to-commit > Fix For: 1.13.0 > > > drillbit.sh can start / stop drillbit. Stop command will stop drillbit > softly. If drillbit is not stopped during pre-defined time, it it will be > killed forcefully (-9). > There is also restart command which basically behaves like stop + start. But > in this case stop command is called without kill forcefully flag. This leads > to the cases when executing restart it hangs since driilbit is not be able to > be killed softly and retries to do it forever. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6192) Drill is vulnerable to CVE-2017-12197
[ https://issues.apache.org/jira/browse/DRILL-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394228#comment-16394228 ] ASF GitHub Bot commented on DRILL-6192: --- Github user asfgit closed the pull request at: https://github.com/apache/drill/pull/1136 > Drill is vulnerable to CVE-2017-12197 > - > > Key: DRILL-6192 > URL: https://issues.apache.org/jira/browse/DRILL-6192 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.12.0 >Reporter: Volodymyr Tkach >Assignee: Volodymyr Tkach >Priority: Major > Labels: ready-to-commit > Fix For: 1.13.0 > > > The current version of libpam4j bundled with MCS does not perform any > authorization check. Any user with valid password could access the cluster > even if the user account is disabled/password expired/'not allowed to access > the service(pam_access ..)' etc.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-5305) Query Profile must display Query ID
[ https://issues.apache.org/jira/browse/DRILL-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-5305: Labels: newbie (was: ) > Query Profile must display Query ID > --- > > Key: DRILL-5305 > URL: https://issues.apache.org/jira/browse/DRILL-5305 > Project: Apache Drill > Issue Type: Improvement > Components: Client - HTTP, Web Server >Affects Versions: 1.10.0 >Reporter: Abhishek Girish >Assignee: Padma Penumarthy >Priority: Minor > Labels: newbie > Fix For: 1.14.0 > > > It would be good to have the query ID, profile ID listed as part of the > profile itself. Currently there is no easy way to map a profile with the > query. > I understand that the profile ID in the URL can be used, but often when we > have profile dumps shared for analysis, they may not contain the query IDs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6044) Shutdown button does not work from WebUI
[ https://issues.apache.org/jira/browse/DRILL-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394095#comment-16394095 ] ASF GitHub Bot commented on DRILL-6044: --- Github user sohami commented on the issue: https://github.com/apache/drill/pull/1153 +1 LGTM. Thanks for making the changes. > Shutdown button does not work from WebUI > > > Key: DRILL-6044 > URL: https://issues.apache.org/jira/browse/DRILL-6044 > Project: Apache Drill > Issue Type: Bug > Components: Client - HTTP >Affects Versions: 1.13.0 >Reporter: Krystal >Assignee: Venkata Jyothsna Donapati >Priority: Critical > Fix For: 1.13.0 > > Attachments: Screen Shot 2017-12-19 at 10.51.16 AM.png > > > git.commit.id.abbrev=eb0c403 > Nothing happens when click on the SHUTDOWN button from the WebUI. The > browser's debugger showed that the request failed due to access control > checks (see attached screen shot). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
