[jira] [Commented] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826563#comment-16826563 ] ASF GitHub Bot commented on DRILL-7201: --- sohami commented on pull request #1767: DRILL-7201: Strange symbols in error window (Windows) URL: https://github.com/apache/drill/pull/1767 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[ https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826562#comment-16826562 ] ASF GitHub Bot commented on DRILL-7213: --- sohami commented on pull request #1766: DRILL-7213: Use dependencySets tag for including artifacts in assembly to consider dependencies from the distribution module URL: https://github.com/apache/drill/pull/1766 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > drill-format-mapr.jar contains stale git.properties file > > > Key: DRILL-7213 > URL: https://issues.apache.org/jira/browse/DRILL-7213 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > For some reason only drill-format-mapr jar in the release candidate tarball > contains a stale git.properties file which is available during the prepare > phase. Other format plugin jar seems fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7207) Update the copyright year in NOTICE.txt file
[ https://issues.apache.org/jira/browse/DRILL-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7207: - Component/s: Tools, Build & Test > Update the copyright year in NOTICE.txt file > > > Key: DRILL-7207 > URL: https://issues.apache.org/jira/browse/DRILL-7207 > Project: Apache Drill > Issue Type: Task > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > Copyright year in NOTICE.txt file is until 2018, we should update it to 2019. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7207) Update the copyright year in NOTICE.txt file
[ https://issues.apache.org/jira/browse/DRILL-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7207: - Labels: ready-to-commit (was: ) > Update the copyright year in NOTICE.txt file > > > Key: DRILL-7207 > URL: https://issues.apache.org/jira/browse/DRILL-7207 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > Copyright year in NOTICE.txt file is until 2018, we should update it to 2019. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7212) Add gpg key with apache.org email for sorabh
[ https://issues.apache.org/jira/browse/DRILL-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7212: - Labels: ready-to-commit (was: ) > Add gpg key with apache.org email for sorabh > > > Key: DRILL-7212 > URL: https://issues.apache.org/jira/browse/DRILL-7212 > Project: Apache Drill > Issue Type: Task > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7207) Update the copyright year in NOTICE.txt file
[ https://issues.apache.org/jira/browse/DRILL-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826561#comment-16826561 ] ASF GitHub Bot commented on DRILL-7207: --- sohami commented on pull request #1768: DRILL-7207: Update the copyright year in NOTICE.txt file URL: https://github.com/apache/drill/pull/1768 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update the copyright year in NOTICE.txt file > > > Key: DRILL-7207 > URL: https://issues.apache.org/jira/browse/DRILL-7207 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > > Copyright year in NOTICE.txt file is until 2018, we should update it to 2019. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7212) Add gpg key with apache.org email for sorabh
[ https://issues.apache.org/jira/browse/DRILL-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826560#comment-16826560 ] ASF GitHub Bot commented on DRILL-7212: --- sohami commented on pull request #1769: DRILL-7212: Add gpg key with apache.org email for sorabh URL: https://github.com/apache/drill/pull/1769 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add gpg key with apache.org email for sorabh > > > Key: DRILL-7212 > URL: https://issues.apache.org/jira/browse/DRILL-7212 > Project: Apache Drill > Issue Type: Task > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826526#comment-16826526 ] ASF GitHub Bot commented on DRILL-7202: --- sohami commented on pull request #1765: DRILL-7202: Failed query shows warning that fragments made no progress URL: https://github.com/apache/drill/pull/1765 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7202: - Component/s: Web Server > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7212) Add gpg key with apache.org email for sorabh
[ https://issues.apache.org/jira/browse/DRILL-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7212: - Component/s: Tools, Build & Test > Add gpg key with apache.org email for sorabh > > > Key: DRILL-7212 > URL: https://issues.apache.org/jira/browse/DRILL-7212 > Project: Apache Drill > Issue Type: Task > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7212) Add gpg key with apache.org email for sorabh
[ https://issues.apache.org/jira/browse/DRILL-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7212: - Reviewer: Boaz Ben-Zvi > Add gpg key with apache.org email for sorabh > > > Key: DRILL-7212 > URL: https://issues.apache.org/jira/browse/DRILL-7212 > Project: Apache Drill > Issue Type: Task > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7212) Add gpg key with apache.org email for sorabh
[ https://issues.apache.org/jira/browse/DRILL-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826510#comment-16826510 ] ASF GitHub Bot commented on DRILL-7212: --- sohami commented on pull request #1769: DRILL-7212: Add gpg key with apache.org email for sorabh URL: https://github.com/apache/drill/pull/1769 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add gpg key with apache.org email for sorabh > > > Key: DRILL-7212 > URL: https://issues.apache.org/jira/browse/DRILL-7212 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-7202: Fix Version/s: (was: 1.17.0) 1.16.0 > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7207) Update the copyright year in NOTICE.txt file
[ https://issues.apache.org/jira/browse/DRILL-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7207: - Reviewer: Boaz Ben-Zvi > Update the copyright year in NOTICE.txt file > > > Key: DRILL-7207 > URL: https://issues.apache.org/jira/browse/DRILL-7207 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > > Copyright year in NOTICE.txt file is until 2018, we should update it to 2019. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7207) Update the copyright year in NOTICE.txt file
[ https://issues.apache.org/jira/browse/DRILL-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826507#comment-16826507 ] ASF GitHub Bot commented on DRILL-7207: --- sohami commented on pull request #1768: DRILL-7207: Update the copyright year in NOTICE.txt file URL: https://github.com/apache/drill/pull/1768 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update the copyright year in NOTICE.txt file > > > Key: DRILL-7207 > URL: https://issues.apache.org/jira/browse/DRILL-7207 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Sorabh Hamirwasia >Priority: Major > Fix For: 1.16.0 > > > Copyright year in NOTICE.txt file is until 2018, we should update it to 2019. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[ https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7213: - Labels: ready-to-commit (was: ) > drill-format-mapr.jar contains stale git.properties file > > > Key: DRILL-7213 > URL: https://issues.apache.org/jira/browse/DRILL-7213 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > For some reason only drill-format-mapr jar in the release candidate tarball > contains a stale git.properties file which is available during the prepare > phase. Other format plugin jar seems fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7201: - Labels: ready-to-commit (was: ) > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-7201: - Component/s: Web Server > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826470#comment-16826470 ] ASF GitHub Bot commented on DRILL-7201: --- kkhatua commented on pull request #1767: DRILL-7201: Strange symbols in error window (Windows) URL: https://github.com/apache/drill/pull/1767 Looks like some unicode characters creeped in, causing the rendering to be messed up ONLY for Windows OS. This PR patches that issue and ensures that the Alert symbol also appears correctly. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826321#comment-16826321
]
Paul Rogers commented on DRILL-7218:
Historically, Drill uses a name-based system for columns rather than the
traditional ordered list. Reason: in file A, you might have (x,y), while in
file B you might have (y,x). Drill treats the schema as a bundle of (unordered)
vectors.
AFAIK, there has been no real discussion about the need for a specified column
order.
This came up in the context of the new scan framework based on the row set
work. That framework *does* attempt to preserve column order. In doing this, it
was very clear that, prior to that work, column order was undefined.
It is also not clear how other operators deal with column order given that
Drill has no schema other than the incoming batches.
So, it might be worth while to determine if column order should be retained,
and, if so, how to ensure consistent ordering in each of the various operators.
(And, more fundamentally, what that order should be in the case in which
readers see different column orders.)
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a":
> "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6974) SET option command
[
https://issues.apache.org/jira/browse/DRILL-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826239#comment-16826239
]
ASF GitHub Bot commented on DRILL-6974:
---
dgrinchenko commented on issue #1763: DRILL-6974: Add possibility to view
option value via SET command
URL: https://github.com/apache/drill/pull/1763#issuecomment-486755985
pushed amend commit with changed commit date to re-trigger travis build. As
it have failed to download deps with [error
503](https://api.travis-ci.org/v3/job/524527531/log.txt).
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> SET option command
> --
>
> Key: DRILL-6974
> URL: https://issues.apache.org/jira/browse/DRILL-6974
> Project: Apache Drill
> Issue Type: Improvement
> Components: SQL Parser
>Affects Versions: 1.15.0
>Reporter: benj
>Assignee: Dmytriy Grinchenko
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.17.0
>
>
> It's currently possible to define options with the SQL command SET
> {code:java}
> ALTER SESSION SET `drill.exec.hashagg.fallback.enabled` = true;
> {code}
> But it's not possible to simply visualize the current value of one option
> with SHOW, we have to query like
> {code:java}
> SELECT * FROM sys.options WHERE `name` =
> 'drill.exec.hashagg.fallback.enabled';
> {code}
> Why not allow a simple
> {code:java}
> SET `drill.exec.hashagg.fallback.enabled`;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7206) Tuning hash join code using primitive int
[ https://issues.apache.org/jira/browse/DRILL-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826200#comment-16826200 ] ASF GitHub Bot commented on DRILL-7206: --- arina-ielchiieva commented on issue #1764: DRILL-7206: using primitive int list at right or full join case URL: https://github.com/apache/drill/pull/1764#issuecomment-486732804 @Ben-Zvi could you please review? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Tuning hash join code using primitive int > - > > Key: DRILL-7206 > URL: https://issues.apache.org/jira/browse/DRILL-7206 > Project: Apache Drill > Issue Type: Improvement >Reporter: weijie.tong >Assignee: weijie.tong >Priority: Major > Fix For: 1.17.0 > > > This issue is try to tune the HashJoin implementation codes. At right or full > join type , the HashJoinProbe will create a List member to record > the unmatched composed indexes. It can be replaced by a primitive > IntArrayList without box/unbox operation ,also benefits the GC if there's > more unmatched items. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (DRILL-7217) VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 to 1.13
[ https://issues.apache.org/jira/browse/DRILL-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826174#comment-16826174 ] Arina Ielchiieva edited comment on DRILL-7217 at 4/25/19 3:37 PM: -- Drill does not guarantee backward compatibility between versions, especially when doing downgrade. For this case, you need to clean up your environment first and then start 1.13 version. was (Author: arina): Drill does not grantee backward compatibility between versions, especially when doing downgrade. For this case, you need to clean up your environment first and then start 1.13 version. > VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 > to 1.13 > > > Key: DRILL-7217 > URL: https://issues.apache.org/jira/browse/DRILL-7217 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.13.0 >Reporter: Dony Dong >Priority: Major > > Hi Team, > We meet an issue after we downgrade from 1.15 to 1.13. > When we query sys.option, it shows this error. > Error: VALIDATION ERROR: The option 'drill.exec.hashjoin.fallback.enabled' > does not exist. > Fragment 0:0 > > Here is what we did. > # upgrade to 1.15. unzip then soft link the dill_home to 1.15 folder. > # change parameter drill.exec.hashjoin.fallback.enabled to true in system > level. > # downgrade by soft link the drill_home to 1.13 folder. > it seems different versions using the same parameter file. > Could you please check this? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7217) VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 to 1.13
[ https://issues.apache.org/jira/browse/DRILL-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826174#comment-16826174 ] Arina Ielchiieva commented on DRILL-7217: - Drill does not grantee backward compatibility between versions, especially when doing downgrade. For this case, you need to clean up your environment first and then start 1.13 version. > VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 > to 1.13 > > > Key: DRILL-7217 > URL: https://issues.apache.org/jira/browse/DRILL-7217 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.13.0 >Reporter: Dony Dong >Priority: Major > > Hi Team, > We meet an issue after we downgrade from 1.15 to 1.13. > When we query sys.option, it shows this error. > Error: VALIDATION ERROR: The option 'drill.exec.hashjoin.fallback.enabled' > does not exist. > Fragment 0:0 > > Here is what we did. > # upgrade to 1.15. unzip then soft link the dill_home to 1.15 folder. > # change parameter drill.exec.hashjoin.fallback.enabled to true in system > level. > # downgrade by soft link the drill_home to 1.13 folder. > it seems different versions using the same parameter file. > Could you please check this? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826164#comment-16826164
]
Volodymyr Vysotskyi commented on DRILL-7218:
There are no such configs. Since it is a map, you can iterate with the list of
the {{columns}} and receive value for the required column for every row.
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a":
> "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826156#comment-16826156
]
Gayathri commented on DRILL-7218:
-
Is there any configuration to preserve the order of columns in rows?
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a":
> "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[ https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-7213: Reviewer: Sorabh Hamirwasia > drill-format-mapr.jar contains stale git.properties file > > > Key: DRILL-7213 > URL: https://issues.apache.org/jira/browse/DRILL-7213 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Volodymyr Vysotskyi >Priority: Major > Fix For: 1.16.0 > > > For some reason only drill-format-mapr jar in the release candidate tarball > contains a stale git.properties file which is available during the prepare > phase. Other format plugin jar seems fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826106#comment-16826106
]
Volodymyr Vysotskyi commented on DRILL-7218:
[~Gayathri01], the order of the columns is preserved in the {{columns}} list.
{{rows}} is just a list of maps, where every map shouldn't preserve the order
of columns.
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a":
> "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayathri updated DRILL-7218:
Description:
When we try to query through Apache Drill REST API, the returned response
doesn't maintain the column order as given in the query.
+Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
dfs.`\files\test.json`"};
*Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
"columns": [
"a",
"b",
"c"
],
"rows": [{
"b": "abc",
"c": " xyz",
"a": "uxv"},
{
"b": "abc",
"c": " xyz",
"a": "uxv"}]
}
Is there any way we can maintain the column order through REST API call?
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [{
> "b": "abc",
> "c": " xyz",
> "a": "uxv"},
> {
> "b": "abc",
> "c": " xyz",
> "a": "uxv"}]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayathri updated DRILL-7218:
Description:
When we try to query through Apache Drill REST API, the returned response
doesn't maintain the column order as given in the query.
+Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
dfs.`\files\test.json`"};
*Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
"columns": [
"a",
"b",
"c"
],
"rows": [
{ "b": "abc", "c": " xyz", "a": "uxv"},
{ "b": "abc", "c": " xyz", "a": "uxv"}
]
}
Is there any way we can maintain the column order through REST API call?
was:
When we try to query through Apache Drill REST API, the returned response
doesn't maintain the column order as given in the query.
+Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
dfs.`\files\test.json`"};
*Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
"columns": [
"a",
"b",
"c"
],
"rows": [{
"b": "abc",
"c": " xyz",
"a": "uxv"},
{
"b": "abc",
"c": " xyz",
"a": "uxv"}]
}
Is there any way we can maintain the column order through REST API call?
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"},
> { "b": "abc", "c": " xyz", "a": "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayathri updated DRILL-7218:
Description:
When we try to query through Apache Drill REST API, the returned response
doesn't maintain the column order as given in the query.
+Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
dfs.`\files\test.json`"};
*Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
"columns": [
"a",
"b",
"c"
],
"rows": [
{ "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a": "uxv"}
]
}
Is there any way we can maintain the column order through REST API call?
was:
When we try to query through Apache Drill REST API, the returned response
doesn't maintain the column order as given in the query.
+Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
dfs.`\files\test.json`"};
*Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
"columns": [
"a",
"b",
"c"
],
"rows": [
{ "b": "abc", "c": " xyz", "a": "uxv"},
{ "b": "abc", "c": " xyz", "a": "uxv"}
]
}
Is there any way we can maintain the column order through REST API call?
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [
> { "b": "abc", "c": " xyz", "a": "uxv"}, \{ "b": "abc", "c": " xyz", "a":
> "uxv"}
> ]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7218) Apache Drill API doesn't preserve the column order
[
https://issues.apache.org/jira/browse/DRILL-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayathri updated DRILL-7218:
Labels: REST_API drill (was: )
> Apache Drill API doesn't preserve the column order
> --
>
> Key: DRILL-7218
> URL: https://issues.apache.org/jira/browse/DRILL-7218
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Priority: Blocker
> Labels: REST_API, drill
>
> When we try to query through Apache Drill REST API, the returned response
> doesn't maintain the column order as given in the query.
> +Example:+ *Request:* \{"queryType" : "SQL","query" : "select a,b,c from
> dfs.`\files\test.json`"};
> *Response:* { "queryId": "233ff474-0902-828b-9efd-0a0bd57eee51",
> "columns": [
> "a",
> "b",
> "c"
> ],
> "rows": [{
> "b": "abc",
> "c": " xyz",
> "a": "uxv"},
> {
> "b": "abc",
> "c": " xyz",
> "a": "uxv"}]
> }
> Is there any way we can maintain the column order through REST API call?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7218) Apache Drill API doesn't preserve the column order
Gayathri created DRILL-7218: --- Summary: Apache Drill API doesn't preserve the column order Key: DRILL-7218 URL: https://issues.apache.org/jira/browse/DRILL-7218 Project: Apache Drill Issue Type: Bug Affects Versions: 1.14.0 Reporter: Gayathri -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[ https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826005#comment-16826005 ] ASF GitHub Bot commented on DRILL-7213: --- vvysotskyi commented on pull request #1766: DRILL-7213: Use dependencySets tag for including artifacts in assembly to consider dependencies from the distribution module URL: https://github.com/apache/drill/pull/1766 For details please see comment under [DRILL-7213](https://issues.apache.org/jira/browse/DRILL-7213). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > drill-format-mapr.jar contains stale git.properties file > > > Key: DRILL-7213 > URL: https://issues.apache.org/jira/browse/DRILL-7213 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Volodymyr Vysotskyi >Priority: Major > Fix For: 1.16.0 > > > For some reason only drill-format-mapr jar in the release candidate tarball > contains a stale git.properties file which is available during the prepare > phase. Other format plugin jar seems fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826002#comment-16826002 ] Arina Ielchiieva commented on DRILL-7201: - Steps to reproduce: 1. Download Windows 10 VM for Virtual box (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) - Virtual machine: MSEdge on Win10 (x64) Stable 1809 - Platform: VirtualBox 2. Unzip and import to Virtual Box 3. Start and login using password: Passw0rd! 4. Install java 8 jdk and environment variable JAVA_HOME 5. Install google chrome 6. Download Drill archive, unzip, start drill-embedded.bat 7. Open link in Chrome: http://localhost:8047/query 8. Click Submit button without query > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-7217) VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 to 1.13
Dony Dong created DRILL-7217: Summary: VALIDATION ERROR: when query sys.option after downgrade the DRILL from 1.15 to 1.13 Key: DRILL-7217 URL: https://issues.apache.org/jira/browse/DRILL-7217 Project: Apache Drill Issue Type: Bug Affects Versions: 1.13.0 Reporter: Dony Dong Hi Team, We meet an issue after we downgrade from 1.15 to 1.13. When we query sys.option, it shows this error. Error: VALIDATION ERROR: The option 'drill.exec.hashjoin.fallback.enabled' does not exist. Fragment 0:0 Here is what we did. # upgrade to 1.15. unzip then soft link the dill_home to 1.15 folder. # change parameter drill.exec.hashjoin.fallback.enabled to true in system level. # downgrade by soft link the drill_home to 1.13 folder. it seems different versions using the same parameter file. Could you please check this? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-7216) Auto limit is happening on the Drill Web-UI while the limit checkbox is unchecked
Anton Gozhiy created DRILL-7216:
---
Summary: Auto limit is happening on the Drill Web-UI while the
limit checkbox is unchecked
Key: DRILL-7216
URL: https://issues.apache.org/jira/browse/DRILL-7216
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Anton Gozhiy
*Steps:*
# On Web-UI, open Query page
# Set "Limit results to" 10, but *not check the checkbox*
# Submit a simple query:
{code:sql}
SELECT * FROM cp.`employee.json` LIMIT 20
{code}
*Expected result:*
Results should be limited be 20 (so as set in the query).
*Actual result:*
Auto limit is applied and the results are limited to 10 rows.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[ https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi reassigned DRILL-7213: -- Assignee: Volodymyr Vysotskyi (was: Sorabh Hamirwasia) > drill-format-mapr.jar contains stale git.properties file > > > Key: DRILL-7213 > URL: https://issues.apache.org/jira/browse/DRILL-7213 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test >Affects Versions: 1.16.0 >Reporter: Sorabh Hamirwasia >Assignee: Volodymyr Vysotskyi >Priority: Major > Fix For: 1.16.0 > > > For some reason only drill-format-mapr jar in the release candidate tarball > contains a stale git.properties file which is available during the prepare > phase. Other format plugin jar seems fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7213) drill-format-mapr.jar contains stale git.properties file
[
https://issues.apache.org/jira/browse/DRILL-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825949#comment-16825949
]
Volodymyr Vysotskyi commented on DRILL-7213:
This issue happens because of the changes made in DRILL-6751. In the scope of
this Jira was changed the way how Jars are included in the assembly. For now,
{{moduleSets/moduleSet}} is used, but such an approach has some issues. The
first one is that it does not handle dependencies added/excluded in the module,
therefore even when {{drill-format-mapr}} dependency is added only for the mapr
profile, it will be included for default profile also, if it was already built
before, so it is the reason for the problem, described in this Jira.
The second issue is that it works correctly when the goal is run for the parent
module, i.e. when the project was built, and {{mvn clean install -pl
distribution}} is executed, module jars wouldn't be included in the assembly.
The solution is to replace back {{moduleSets}} with the {{dependencySets}}.
> drill-format-mapr.jar contains stale git.properties file
>
>
> Key: DRILL-7213
> URL: https://issues.apache.org/jira/browse/DRILL-7213
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
>Affects Versions: 1.16.0
>Reporter: Sorabh Hamirwasia
>Assignee: Sorabh Hamirwasia
>Priority: Major
> Fix For: 1.16.0
>
>
> For some reason only drill-format-mapr jar in the release candidate tarball
> contains a stale git.properties file which is available during the prepare
> phase. Other format plugin jar seems fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-7202: Reviewer: Arina Ielchiieva > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Labels: ready-to-commit > Fix For: 1.17.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825832#comment-16825832 ] ASF GitHub Bot commented on DRILL-7202: --- arina-ielchiieva commented on issue #1765: DRILL-7202: Failed query shows warning that fragments made no progress URL: https://github.com/apache/drill/pull/1765#issuecomment-486559975 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Fix For: 1.17.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7202) Failed query shows warning that fragments has made no progress
[ https://issues.apache.org/jira/browse/DRILL-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-7202: Labels: ready-to-commit (was: ) > Failed query shows warning that fragments has made no progress > -- > > Key: DRILL-7202 > URL: https://issues.apache.org/jira/browse/DRILL-7202 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Minor > Labels: ready-to-commit > Fix For: 1.17.0 > > Attachments: FailedQuery_NoProgressWarning_Repro_Attempt.png, > no_fragments_progress_warning.JPG > > > Failed query shows warning that fragments has made no progress. > Since query failed during planning stage and did not have any fragments, > looks strange to see such warning. Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7201) Strange symbols in error window (Windows)
[ https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-7201: Priority: Major (was: Blocker) > Strange symbols in error window (Windows) > - > > Key: DRILL-7201 > URL: https://issues.apache.org/jira/browse/DRILL-7201 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Arina Ielchiieva >Assignee: Kunal Khatua >Priority: Major > Fix For: 1.16.0 > > Attachments: error_window.JPG, error_with_symbols.png, > image-2019-04-24-10-22-30-830.png, inspect-element-font.png > > > Error window contains strange symbols on Windows, works fine on other OS. > Before we had alert instead which did not have such issue. > Screenshot attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7201) Strange symbols in error window (Windows)
[
https://issues.apache.org/jira/browse/DRILL-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825830#comment-16825830
]
Arina Ielchiieva commented on DRILL-7201:
-
On my last screenshot, you can see that {{font-family: 'Glyphicons Halflings'}}
is set initially (use scroll to see full screenshot). Not sure its a
localization issue since my locale is US. Regarding blocker, it there will be
new rc, it would be nice to fix this one as well.
> Strange symbols in error window (Windows)
> -
>
> Key: DRILL-7201
> URL: https://issues.apache.org/jira/browse/DRILL-7201
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Arina Ielchiieva
>Assignee: Kunal Khatua
>Priority: Blocker
> Fix For: 1.16.0
>
> Attachments: error_window.JPG, error_with_symbols.png,
> image-2019-04-24-10-22-30-830.png, inspect-element-font.png
>
>
> Error window contains strange symbols on Windows, works fine on other OS.
> Before we had alert instead which did not have such issue.
> Screenshot attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7135) Upgrade to Jetty 9.4
[ https://issues.apache.org/jira/browse/DRILL-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825805#comment-16825805 ] Ayush Sharma commented on DRILL-7135: - Kindly make sure we use the Latest Jetty version for 9.4 as the initial few versions are vulnerable and contains CVEs. > Upgrade to Jetty 9.4 > > > Key: DRILL-7135 > URL: https://issues.apache.org/jira/browse/DRILL-7135 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Vitalii Diravka >Priority: Minor > Fix For: 1.17.0 > > > Initially DRILL-7051 updated Jetty to 9.4 version and DRILL-7081 updated > Jersey version to 2.28 version. These versions work fine for Drill with > Hadoop version below 3.0. > Starting from Hadoop 3.0 it uses > [org.eclipse.jetty|https://github.com/apache/hadoop/blob/branch-3.0/hadoop-project/pom.xml#L38] > 9.3 version. > That's why it conflicts with newer Jetty&Jersey versions. > Drill can update Jetty and Jersey versions after resolution HADOOP-14930 and > HBASE-19256. > Or alternatively these libs can be shaded in Drill, but there is no real > reason to do it nowadays. > See details in > [#1681|https://github.com/apache/drill/pull/1681#discussion_r265904521] PR. > _Notes_: > * For Jersey update it is necessary to add > org.glassfish.jersey.inject:jersey-hk2 in Drill to solve all compilation > failures. > * See doc for Jetty update: > https://www.eclipse.org/jetty/documentation/9.4.x/upgrading-jetty.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7215) Null error shown when select file without format
[
https://issues.apache.org/jira/browse/DRILL-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-7215:
Fix Version/s: Future
> Null error shown when select file without format
>
>
> Key: DRILL-7215
> URL: https://issues.apache.org/jira/browse/DRILL-7215
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Igor Guzenko
>Priority: Minor
> Fix For: Future
>
>
> Null error message is shown while querying file without format after use
> schema:
> {code:none}
> select * from `dir/noformat`;
> Error: VALIDATION ERROR: null
> [Error Id: b9e3e3a4-f60a-4836-97e9-6078c742f7ad ] (state=,code=0)
> {code}
>
> Steps to reproduce:
> # Create dir and file w/o format:
> {code:java}
> mkdir /tmp/dir&&touch /tmp/dir/noformat{code}
> # Run drill in embedded mode
> # Use tmp schema
> {code:sql}
> USE dfs.tmp; {code}
> # Query created file
> {code:sql}
> SELECT * FROM `dir/noformat`;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7215) Null error shown when select file without format
Igor Guzenko created DRILL-7215:
---
Summary: Null error shown when select file without format
Key: DRILL-7215
URL: https://issues.apache.org/jira/browse/DRILL-7215
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0, 1.16.0
Reporter: Igor Guzenko
Null error message is shown while querying file without format after use
schema:
{code:none}
select * from `dir/noformat`;
Error: VALIDATION ERROR: null
[Error Id: b9e3e3a4-f60a-4836-97e9-6078c742f7ad ] (state=,code=0)
{code}
Steps to reproduce:
# Create dir and file w/o format:
{code:java}
mkdir /tmp/dir&&touch /tmp/dir/noformat{code}
# Run drill in embedded mode
# Use tmp schema
{code:sql}
USE dfs.tmp; {code}
# Query created file
{code:sql}
SELECT * FROM `dir/noformat`;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
