[jira] [Commented] (TRAFODION-2159) Unnest correlated subquery with explicit groupby
[ https://issues.apache.org/jira/browse/TRAFODION-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419806#comment-15419806 ] ASF GitHub Bot commented on TRAFODION-2159: --- GitHub user sureshsubbiah opened a pull request: https://github.com/apache/incubator-trafodion/pull/657 [TRAFODION-2159] Unnest correlated subquery with explicit groupby Add support for unnesting subqueries with a groupby in addition to the scalar aggregate. Only 1 level of subquery is current supported. Also unnesting that requires left join is excluded from this change. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sureshsubbiah/incubator-trafodion unnest1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/657.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 #657 commit 24e252c1c00c9a4d26d0b233d8047c25b089c845 Author: Suresh Subbiah Date: 2016-08-05T21:50:58Z Intial change for unnesting commit f0cae7f83395f1f16c702efda4f1dbc427bebefa Author: Suresh Subbiah Date: 2016-08-13T04:53:48Z Subquery unnest for subquery with explicit groupby > Unnest correlated subquery with explicit groupby > > > Key: TRAFODION-2159 > URL: https://issues.apache.org/jira/browse/TRAFODION-2159 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Suresh Subbiah > Fix For: 2.1-incubating > > Attachments: GroupByUnnest.pdf > > > Correlated subqueries with the pattern shown on the left side of the > attachment are currently not unnested. When cqd subquery_unnesting is set to > 'DEBUG' this warning message is seen > *** WARNING[2997] (Subquery was not unnested. Reason: Right grandchild of > TSJ is a semijoin or a group by) > An example query is > prepare XX from > select t40.a > from t40 > where t40.b >= (select avg(counta) from (select count(a) as counta from t44 > where t40.c = t44.b group by t44.c)) ; > > Here the "group by t44.c" in the subquery prevents it from being unnested, > while "t40.c = t44.b" is the correlation predicate. > With the transformation shown in the right side of the attachment this query > will be unnested to this equivalent form, which has no explicit correlation > select a0 from > (select a0, avg(counta4) avga4 from > (select a0, b0, count(a4) counta4 from > (select t40.a a0, t40.b b0, t44.a a4, t44.c c4 from > t40,t44 > where t40.c = t44.b )T1(a0,b0,a4,c4) > group by (a0,b0,c4)) T2(a0,b0,counta4) > group by (a0,b0) > having b0 >= avga4) T3(a0, avga4) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2161) Metadata upgrade failed when there is user view on repository tables
Gao, Rui-Xian created TRAFODION-2161: Summary: Metadata upgrade failed when there is user view on repository tables Key: TRAFODION-2161 URL: https://issues.apache.org/jira/browse/TRAFODION-2161 Project: Apache Trafodion Issue Type: Bug Components: sql-cmu Environment: centos6.7 CDH5.4.8 esgynDB R2.2 0811 daily build Reporter: Gao, Rui-Xian Assignee: Roberta Marton [trafodion@centosqa-1 ~]$ sqlci EsgynDB Advanced Conversational Interface 2.2.0 Copyright (c) 2015-2016 Esgyn Corporation >>get schemas; *** ERROR[1395] Trafodion needs to be upgraded on this system due to metadata version mismatch. Do 'initialize trafodion, upgrade' to upgrade metadata. Or do 'initialize trafodion, drop' followed by 'initialize trafodion'. Be aware that the second option will delete all metadata and user objects from Trafodion database . *** ERROR[8822] The statement was not prepared. >>initialize trafodion, upgrade; Metadata Upgrade: started Version Check: started Metadata needs to be upgraded from Version 1.0.1 to 2.1.0. Upgrade needed for Catalogs, Privileges, Repository. Version Check: done Drop Old Metadata: started Drop Old Metadata: done Backup Current Metadata: started Backup Current Metadata: done Drop Current Metadata: started Drop Current Metadata: done Initialize New Metadata: started Initialize New Metadata: done Copy Old Metadata: started Copy Old Metadata: done Validate Metadata Copy: started Validate Metadata Copy: done Delete Old Metadata Info: started Delete Old Metadata Info: done Upgrade Repository: Started Start: Drop Old Repository End: Drop Old Repository Start: Rename Current Repository Upgrade Repository: Restoring Old Repository Start: Rename Old Repository back to New End: Rename Old Repository back to New Upgrade Repository: Restore done Drop Old Metadata: started Drop Old Metadata: done Metadata Upgrade: failed *** ERROR[1427] Table cannot be renamed. Reason: Operation not allowed if dependent views exist. Drop the views and recreate them after rename. *** ERROR[8839] Transaction was aborted. --- SQL operation failed with errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2157) add built-in support of popular MySQL functions
[ https://issues.apache.org/jira/browse/TRAFODION-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2157: --- Assignee: liu ming > add built-in support of popular MySQL functions > --- > > Key: TRAFODION-2157 > URL: https://issues.apache.org/jira/browse/TRAFODION-2157 > Project: Apache Trafodion > Issue Type: Umbrella >Reporter: liu ming >Assignee: liu ming > > To make migration easier, it will be great to add support for those very > popular MySQL functions. > For example GROUP_CONCAT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2157) add built-in support of popular MySQL functions
[ https://issues.apache.org/jira/browse/TRAFODION-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2157 started by liu ming. --- > add built-in support of popular MySQL functions > --- > > Key: TRAFODION-2157 > URL: https://issues.apache.org/jira/browse/TRAFODION-2157 > Project: Apache Trafodion > Issue Type: Umbrella >Reporter: liu ming >Assignee: liu ming > > To make migration easier, it will be great to add support for those very > popular MySQL functions. > For example GROUP_CONCAT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2160) Metadata upgrade failed with internal error in PrivMgrMD.cpp
[ https://issues.apache.org/jira/browse/TRAFODION-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419690#comment-15419690 ] ASF GitHub Bot commented on TRAFODION-2160: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/656 > Metadata upgrade failed with internal error in PrivMgrMD.cpp > > > Key: TRAFODION-2160 > URL: https://issues.apache.org/jira/browse/TRAFODION-2160 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Roberta Marton >Assignee: Roberta Marton > > Metadata Upgrade: failed > > > *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp > on line 326. DETAILS(Expecting 133 component privileges, instead 140 were > found.). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2160) Metadata upgrade failed with internal error in PrivMgrMD.cpp
[ https://issues.apache.org/jira/browse/TRAFODION-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419461#comment-15419461 ] ASF GitHub Bot commented on TRAFODION-2160: --- GitHub user robertamarton opened a pull request: https://github.com/apache/incubator-trafodion/pull/656 [TRAFODION-2160]: Metadata upgrade failed with internal error in Priv… …MgrMD.cpp Fixed a check that verifies component privilege grants were sufficient during upgrade Updated expected results for privs2/TEST143 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertamarton/incubator-trafodion trafodion-2160 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/656.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 #656 commit 5f1ca3885a33a3d3d711b3a70ebec9156855a1e0 Author: Roberta Marton Date: 2016-08-12T20:44:58Z [TRAFODION-2160]: Metadata upgrade failed with internal error in PrivMgrMD.cpp Fixed a check that verifies component privilege grants were sufficient during upgrade Updated expected results for privs2/TEST143 > Metadata upgrade failed with internal error in PrivMgrMD.cpp > > > Key: TRAFODION-2160 > URL: https://issues.apache.org/jira/browse/TRAFODION-2160 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Roberta Marton >Assignee: Roberta Marton > > Metadata Upgrade: failed > > > *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp > on line 326. DETAILS(Expecting 133 component privileges, instead 140 were > found.). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2160) Metadata upgrade failed with internal error in PrivMgrMD.cpp
[ https://issues.apache.org/jira/browse/TRAFODION-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419440#comment-15419440 ] Roberta Marton commented on TRAFODION-2160: --- Upgrade calls initialize authorization to add any new component privileges for the latest release. The code verifies that all the system grants are performed but did not take into consideration any grants that the customer might add. The check has been changed to take this into account. > Metadata upgrade failed with internal error in PrivMgrMD.cpp > > > Key: TRAFODION-2160 > URL: https://issues.apache.org/jira/browse/TRAFODION-2160 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Roberta Marton >Assignee: Roberta Marton > > Metadata Upgrade: failed > > > *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp > on line 326. DETAILS(Expecting 133 component privileges, instead 140 were > found.). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2160) Metadata upgrade failed with internal error in PrivMgrMD.cpp
[ https://issues.apache.org/jira/browse/TRAFODION-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2160 started by Roberta Marton. - > Metadata upgrade failed with internal error in PrivMgrMD.cpp > > > Key: TRAFODION-2160 > URL: https://issues.apache.org/jira/browse/TRAFODION-2160 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Roberta Marton >Assignee: Roberta Marton > > Metadata Upgrade: failed > > > *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp > on line 326. DETAILS(Expecting 133 component privileges, instead 140 were > found.). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2160) Metadata upgrade failed with internal error in PrivMgrMD.cpp
Roberta Marton created TRAFODION-2160: - Summary: Metadata upgrade failed with internal error in PrivMgrMD.cpp Key: TRAFODION-2160 URL: https://issues.apache.org/jira/browse/TRAFODION-2160 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Roberta Marton Assignee: Roberta Marton Metadata Upgrade: failed *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp on line 326. DETAILS(Expecting 133 component privileges, instead 140 were found.). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2159) Unnest correlated subquery with explicit groupby
[ https://issues.apache.org/jira/browse/TRAFODION-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419109#comment-15419109 ] Suresh Subbiah commented on TRAFODION-2159: --- The transformation will be done in the PullUpGroupByTransformation method, which is part of the SemanticQueryOptimization (SQO) phase. During this phase we currently pull up a scalar aggregate (Group by with no grouping cols) over TSJ, absorb Filter predicate into newJoin, and convert TSJ into newJoin. With this change we will in addition pullup the explicit subquery groupBy too (along with the scalar aggregate). So two groupbys which where on the right side of TSJ will now will move to be parent of a join. They will keep their relative order. Key of left side of join will be ADDED to grouping column of both GBs. Its a simple transformation, pullup the explicit groupby in the exact same way as the scalar aggregate groupby, with a similar change to its grouping cols (i.e. addition of left side key) A small change is needed in createFilterChildIfNecessary method, since we want to place the Filter node below the explicit groupby node. Current code expects Filter to be right grandchild of TSJ, but now it could be right grandchild or right grand-grand child. If the subquery requires a moveUpgroupby transformation (used when there are two or more levels of nested subqueries) then this change is disabled. Moveup groupby transformation does something similar, but here the second groupby comes from a different subquery. This restriction can be relaxed later. This change will also not kick in if the subquery does not contain a null rejecting predicate (i.e. contains an OR predicate for example). In this case we need a Left join to unnest, which require a MapValueId node near the groupby. Since the interaction between MapvalueId and this new groupby has not been fully explored, this is restricted for now > Unnest correlated subquery with explicit groupby > > > Key: TRAFODION-2159 > URL: https://issues.apache.org/jira/browse/TRAFODION-2159 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Suresh Subbiah > Fix For: 2.1-incubating > > Attachments: GroupByUnnest.pdf > > > Correlated subqueries with the pattern shown on the left side of the > attachment are currently not unnested. When cqd subquery_unnesting is set to > 'DEBUG' this warning message is seen > *** WARNING[2997] (Subquery was not unnested. Reason: Right grandchild of > TSJ is a semijoin or a group by) > An example query is > prepare XX from > select t40.a > from t40 > where t40.b >= (select avg(counta) from (select count(a) as counta from t44 > where t40.c = t44.b group by t44.c)) ; > > Here the "group by t44.c" in the subquery prevents it from being unnested, > while "t40.c = t44.b" is the correlation predicate. > With the transformation shown in the right side of the attachment this query > will be unnested to this equivalent form, which has no explicit correlation > select a0 from > (select a0, avg(counta4) avga4 from > (select a0, b0, count(a4) counta4 from > (select t40.a a0, t40.b b0, t44.a a4, t44.c c4 from > t40,t44 > where t40.c = t44.b )T1(a0,b0,a4,c4) > group by (a0,b0,c4)) T2(a0,b0,counta4) > group by (a0,b0) > having b0 >= avga4) T3(a0, avga4) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2159) Unnest correlated subquery with explicit groupby
[ https://issues.apache.org/jira/browse/TRAFODION-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Subbiah updated TRAFODION-2159: -- Attachment: GroupByUnnest.pdf > Unnest correlated subquery with explicit groupby > > > Key: TRAFODION-2159 > URL: https://issues.apache.org/jira/browse/TRAFODION-2159 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Suresh Subbiah > Fix For: 2.1-incubating > > Attachments: GroupByUnnest.pdf > > > Correlated subqueries with the pattern shown on the left side of the > attachment are currently not unnested. When cqd subquery_unnesting is set to > 'DEBUG' this warning message is seen > *** WARNING[2997] (Subquery was not unnested. Reason: Right grandchild of > TSJ is a semijoin or a group by) > An example query is > prepare XX from > select t40.a > from t40 > where t40.b >= (select avg(counta) from (select count(a) as counta from t44 > where t40.c = t44.b group by t44.c)) ; > > Here the "group by t44.c" in the subquery prevents it from being unnested, > while "t40.c = t44.b" is the correlation predicate. > With the transformation shown in the right side of the attachment this query > will be unnested to this equivalent form, which has no explicit correlation > select a0 from > (select a0, avg(counta4) avga4 from > (select a0, b0, count(a4) counta4 from > (select t40.a a0, t40.b b0, t44.a a4, t44.c c4 from > t40,t44 > where t40.c = t44.b )T1(a0,b0,a4,c4) > group by (a0,b0,c4)) T2(a0,b0,counta4) > group by (a0,b0) > having b0 >= avga4) T3(a0, avga4) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2159) Unnest correlated subquery with explicit groupby
Suresh Subbiah created TRAFODION-2159: - Summary: Unnest correlated subquery with explicit groupby Key: TRAFODION-2159 URL: https://issues.apache.org/jira/browse/TRAFODION-2159 Project: Apache Trafodion Issue Type: Bug Components: sql-cmp Affects Versions: 2.0-incubating Reporter: Suresh Subbiah Assignee: Suresh Subbiah Fix For: 2.1-incubating Correlated subqueries with the pattern shown on the left side of the attachment are currently not unnested. When cqd subquery_unnesting is set to 'DEBUG' this warning message is seen *** WARNING[2997] (Subquery was not unnested. Reason: Right grandchild of TSJ is a semijoin or a group by) An example query is prepare XX from select t40.a from t40 where t40.b >= (select avg(counta) from (select count(a) as counta from t44 where t40.c = t44.b group by t44.c)) ; Here the "group by t44.c" in the subquery prevents it from being unnested, while "t40.c = t44.b" is the correlation predicate. With the transformation shown in the right side of the attachment this query will be unnested to this equivalent form, which has no explicit correlation select a0 from (select a0, avg(counta4) avga4 from (select a0, b0, count(a4) counta4 from (select t40.a a0, t40.b b0, t44.a a4, t44.c c4 from t40,t44 where t40.c = t44.b )T1(a0,b0,a4,c4) group by (a0,b0,c4)) T2(a0,b0,counta4) group by (a0,b0) having b0 >= avga4) T3(a0, avga4) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2158) Various fixes, several related to tinyint
[ https://issues.apache.org/jira/browse/TRAFODION-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419002#comment-15419002 ] Suresh Subbiah commented on TRAFODION-2158: --- Resolved with https://github.com/apache/incubator-trafodion/pull/654 > Various fixes, several related to tinyint > - > > Key: TRAFODION-2158 > URL: https://issues.apache.org/jira/browse/TRAFODION-2158 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Anoop Sharma > > --error message returned during string to float conversion error was not > correct. That has been fixed. > -- ordering was not getting set correctly during key encoding. > -- stored descriptor was not getting stored correctly if > the generated length was exactly 1 bytes (max length of TEXT.text col). > -- time part of european date format is now handled correctly > by using '.' as delimiter instead of ':' > -- repeat function was crashing if specified maxlength was not sufficient > to hold the result. It now returns an overflow error. > -- tinyint key columns were not handling the case of overflow/underflow > when used in a key predicate. That has been fixed. > -- Numeric datatype with precision less than 3 is now created as tinyint > and handled in expressions. > -- some non-tinyint datatypes(float, decimal) were not being handled > correctly when converted to tinyint. That has been fixed. > -- some more pcode instructions involving tinyint range check and > conversions have been added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2141) Provide cluster view of region stats over all regions.
[ https://issues.apache.org/jira/browse/TRAFODION-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Subbiah resolved TRAFODION-2141. --- Resolution: Fixed > Provide cluster view of region stats over all regions. > -- > > Key: TRAFODION-2141 > URL: https://issues.apache.org/jira/browse/TRAFODION-2141 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: Anoop Sharma >Assignee: Anoop Sharma >Priority: Minor > > Add support to return hbase stats over all regions and region > servers by providing cluster view of returned stats. > In addition, add a new column, region_server, to current region > stats virtual table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2158) Various fixes, several related to tinyint
[ https://issues.apache.org/jira/browse/TRAFODION-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Subbiah resolved TRAFODION-2158. --- Resolution: Fixed > Various fixes, several related to tinyint > - > > Key: TRAFODION-2158 > URL: https://issues.apache.org/jira/browse/TRAFODION-2158 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Anoop Sharma > > --error message returned during string to float conversion error was not > correct. That has been fixed. > -- ordering was not getting set correctly during key encoding. > -- stored descriptor was not getting stored correctly if > the generated length was exactly 1 bytes (max length of TEXT.text col). > -- time part of european date format is now handled correctly > by using '.' as delimiter instead of ':' > -- repeat function was crashing if specified maxlength was not sufficient > to hold the result. It now returns an overflow error. > -- tinyint key columns were not handling the case of overflow/underflow > when used in a key predicate. That has been fixed. > -- Numeric datatype with precision less than 3 is now created as tinyint > and handled in expressions. > -- some non-tinyint datatypes(float, decimal) were not being handled > correctly when converted to tinyint. That has been fixed. > -- some more pcode instructions involving tinyint range check and > conversions have been added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2158) Various fixes, several related to tinyint
Suresh Subbiah created TRAFODION-2158: - Summary: Various fixes, several related to tinyint Key: TRAFODION-2158 URL: https://issues.apache.org/jira/browse/TRAFODION-2158 Project: Apache Trafodion Issue Type: Bug Components: sql-general Affects Versions: 2.0-incubating Reporter: Suresh Subbiah Assignee: Anoop Sharma --error message returned during string to float conversion error was not correct. That has been fixed. -- ordering was not getting set correctly during key encoding. -- stored descriptor was not getting stored correctly if the generated length was exactly 1 bytes (max length of TEXT.text col). -- time part of european date format is now handled correctly by using '.' as delimiter instead of ':' -- repeat function was crashing if specified maxlength was not sufficient to hold the result. It now returns an overflow error. -- tinyint key columns were not handling the case of overflow/underflow when used in a key predicate. That has been fixed. -- Numeric datatype with precision less than 3 is now created as tinyint and handled in expressions. -- some non-tinyint datatypes(float, decimal) were not being handled correctly when converted to tinyint. That has been fixed. -- some more pcode instructions involving tinyint range check and conversions have been added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2104) odb crashed when extract single table using xml format in linux
[ https://issues.apache.org/jira/browse/TRAFODION-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418956#comment-15418956 ] ASF GitHub Bot commented on TRAFODION-2104: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/653 > odb crashed when extract single table using xml format in linux > --- > > Key: TRAFODION-2104 > URL: https://issues.apache.org/jira/browse/TRAFODION-2104 > Project: Apache Trafodion > Issue Type: Bug > Environment: centos6.7 > HBase 1.0.0 - cdh 5.4.8 >Reporter: zhangliang >Assignee: zhangliang >Priority: Minor > > function pass and extract correct file, but odb crashed at last > Usecase : Extract single table using xml format > Command : ./odb64luo -u trafodion -p traf123 -d traf -e > src=trafodion.odb_test_extract.person_e:tgt=output_data/ext_xml_%t.csv:rows=m10:fs=,:trim:sq=\":xml > Result : failed > During : 14s > Details : > Connected to Trafodion > [0] odb(13001) [2016-07-07 16:58:37] - [Trafodion ODBC Driver][Trafodion > Database] SQL WARNING:*** WARNING[6008] Statistics for column (PID) from > table TRAFODION.ODB_TEST_EXTRACT.PERSON_E were not available. As a result, > the access path chosen might not be the best possible. [2016-07-07 16:58:17] > (State: 01000 Native Err: 6008) > odb [2016-07-07 16:58:37]: starting ODBC connection(s)... 0 > [0] odb(3206) [2016-07-07 16:58:38] - [Trafodion ODBC Driver][Trafodion > Database] SQL WARNING:*** WARNING[6008] Statistics for column (PID) from > table TRAFODION.ODB_TEST_EXTRACT.PERSON_E were not available. As a result, > the access path chosen might not be the best possible. [2016-07-07 16:58:18] > (State: 01000 Native Err: 6008) > [0] 29,704 records extracted > [0] 59,408 records extracted > [0] 89,112 records extracted > [0] 118,816 records extracted > [0] 148,520 records extracted > [0] 178,224 records extracted > [0] 207,928 records extracted > [0] 237,632 records extracted > [0] 267,336 records extracted > [0] 297,040 records extracted > [0] 326,744 records extracted > [0] 356,448 records extracted > [0] 386,152 records extracted > [0] 415,856 records extracted > [0] 445,560 records extracted > [0] 475,264 records extracted > [0] 504,968 records extracted > [0] 534,672 records extracted > [0] 564,376 records extracted > [0] 594,080 records extracted > [0] 623,784 records extracted > [0] 653,488 records extracted > [0] 683,192 records extracted > [0] 712,896 records extracted > [0] 742,600 records extracted > [0] 772,304 records extracted > [0] 802,008 records extracted > [0] 831,712 records extracted > [0] 861,416 records extracted > [0] 891,120 records extracted > [0] 920,824 records extracted > [0] 950,528 records extracted > [0] 980,232 records extracted > [0] 1,000,000 records extracted > sh: line 1: 34333 Segmentation fault ./odb64luo -u trafodion -p traf123 > -d traf -e > src=trafodion.odb_test_extract.person_e:tgt=output_data/ext_xml_%t.csv:rows=m10:fs=,:trim:sq=\":xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2157) add built-in support of popular MySQL functions
liu ming created TRAFODION-2157: --- Summary: add built-in support of popular MySQL functions Key: TRAFODION-2157 URL: https://issues.apache.org/jira/browse/TRAFODION-2157 Project: Apache Trafodion Issue Type: Umbrella Reporter: liu ming To make migration easier, it will be great to add support for those very popular MySQL functions. For example GROUP_CONCAT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2136) union all can't work efficiently
[
https://issues.apache.org/jira/browse/TRAFODION-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liu ming reassigned TRAFODION-2136:
---
Assignee: liu ming
> union all can't work efficiently
>
>
> Key: TRAFODION-2136
> URL: https://issues.apache.org/jira/browse/TRAFODION-2136
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
>Affects Versions: any
>Reporter: Joshua Liu
>Assignee: liu ming
>
> there is one query called a
> the first time we run
> a;
> and get the elapsed time time1
> reconnect the database;
> the second time we run
> a union all a;
> and get another elapsed time.time2
> here time2 ≈ time1*2
> -
> see below for detailed info
> a is
> select count(*)
> from F_INCOME_DAY_RH a left join D_IN_SORTCODE_NEW b
> on (A.INCOMESORTCODE_N = B.CODE1)
> where (((a.BBQ >= date '2014-01-01') AND (a.BBQ <= date '2014-12-31')) AND
> ((a.BUDGETLEVEL = '3') AND
> ((a.TAXORGCODE in ('1', '2', '3', '4', '5'))) AND
> (a.DISTRICT_CO_CODE like 'A%' or
> a.DISTRICT_CO_CODE like 'B%')) AND
> ((a.INCOMESORTCODE_N LIKE 'A%') OR
> (a.INCOMESORTCODE_N LIKE 'B%') OR
> (a.INCOMESORTCODE_N LIKE 'C%') OR
> (a.INCOMESORTCODE_N LIKE 'F%') OR
> (a.INCOMESORTCODE_N LIKE 'G%')))
> group by b.CODE5
> -
> SQL>explain options 'f' s1;
>
> LC RC OP OPERATOR OPT DESCRIPTION CARD
> -
>
> 7.8root 6.00E+000
> 6.7hash_partial_groupby 6.00E+000
> 5.6esp_exchange1:16(hash2) 6.00E+000
> 4.5hash_partial_groupby 6.00E+000
> 324left_hybrid_hash_joi 1.06E+006
> ..3trafodion_scan F_INCOME_DAY_RH 1.06E+006
> 1.2esp_exchange16(rep-b):1 (m) 7.24E+002
> ..1trafodion_scan D_IN_SORTCODE_NEW 7.24E+002
> --- SQL operation complete.
> SQL>set statistics on;
> SQL>execute s1;
> (EXPR)
>
> 977626
>16080
>34817
>53722
> 5573
> --- 5 row(s) selected.
>
> Start Time 2016/07/30 09:47:50.913298
> End Time 2016/07/30 09:48:05.018125
> Elapsed Time 00:00:14.104827
> Compile Time 00:00:05.641437
> Execution Time00:00:14.104827
> ---
> reconnect database and run a union all a;
> SQL>explain options 'f' s1;
>
> LC RC OP OPERATOR OPT DESCRIPTION CARD
> -
>
> 15 .16 root 1.20E+001
> 714 15 merge_union 1.20E+001
> 13 .14 hash_partial_groupby 6.00E+000
> 12 .13 esp_exchange1:16(hash2) 6.00E+000
> 11 .12 hash_partial_groupby 6.00E+000
> 10 911 left_hybrid_hash_joi 1.06E+006
> ..10 trafodion_scan F_INCOME_DAY_RH 1.06E+006
> 8.9esp_exchange16(rep-b):1 (m) 7.24E+002
> ..8trafodion_scan D_IN_SORTCODE_NEW 7.24E+002
> 6.7hash_partial_groupby 6.00E+000
> 5.6esp_exchange1:16(hash2) 6.00E+000
> 4.5hash_partial_groupby 6.00E+000
> 324left_hybrid_hash_joi 1.06E+006
> ..3trafodion_scan F_INCOME_DAY_RH 1.06E+006
> 1.2esp_exchange16(rep-b):1 (m) 7.24E+002
> ..1trafodion_scan D_IN_SORTCODE_NEW 7.24E+002
> --- SQL operation complete.
>
> Start Time 2016/07/30 09:48:28.230061
> End Time 2016/07/30 09:48:45.506429
> Elapsed Time 00:00:17.276368
> Compile Time 00:00:17.276368
> Execution Time00:00:00.00
>
> SQL>execute s1;
> (EXPR)
>
> 977626
>16080
>34817
>53722
> 5573
> 977626
>16080
>
[jira] [Commented] (TRAFODION-2067) Support CDH 5.7
[ https://issues.apache.org/jira/browse/TRAFODION-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418318#comment-15418318 ] ASF GitHub Bot commented on TRAFODION-2067: --- GitHub user mashengchen opened a pull request: https://github.com/apache/incubator-trafodion/pull/655 TRAFODION-2067 support cdh5.7 & hbase1.2 previous PR #610 has some conflict. do a new PR 1. support cdh5.7 & hbase1.2. add hbase-trx-cdh5.7.jar & hbase-trx-apache1.2.jar 2. HBASE_DISTRO add CDH5.7 APACHE1.2 3. remove cdh & apache & cdh version in trafodion-dtm-.jar & trafodion-sql-.jar & trafodion-utility-.jar, they will be trafodion-dtm-[apache][cdh][hdp]-$trafodion_version.jar & trafodion-sql-[apache][cdh][hdp]-$trafodion_version.jar & trafodion-utility-$trafodion_version.jar . becacuse we can't determine which version user will install. and we only have one version of each jar. but not hbase-trx.jar, so hbase-trx*.jar have version, because they have multi version. eg: for cdh they have hbase-trx-cdh5_4-2.1.0.jar & hbase-trx-cdh5_5-2.1.0.jar & hbase-trx-cdh5_7-2.1.0.jar 4. HBASE1.* ->APACHE1.* in .tmpl files. 5. do some optimize in traf_config_check You can merge this pull request into a Git repository by running: $ git pull https://github.com/mashengchen/incubator-trafodion cdh5.7 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/655.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 #655 commit 7329e015b62c13ee62d80240ace1766519de7c19 Author: mashengchen Date: 2016-08-12T03:06:42Z TRAFODION-2067 support cdh5.7 & hbase1.2 commit e1799e431465d108a226ce726b1d21b28a3eaf9d Author: mashengchen Date: 2016-08-12T03:41:55Z update SsccRegionEndpoint.java.tmpl > Support CDH 5.7 > --- > > Key: TRAFODION-2067 > URL: https://issues.apache.org/jira/browse/TRAFODION-2067 > Project: Apache Trafodion > Issue Type: Improvement > Environment: CDH 5.7 >Reporter: yuhong zhou >Assignee: mashengchen > > our bigdata platform CDH had been upgraded to 5.7. As tring to apply apache > trafodion as data warehouse based on bigdata distributions, we found current > release couldn;t support CDH 5.7 ,we wish next release can support it . > additionally, apache trafodion should be close to mainstream open soure > bigdata platform release, So， apache trafodion can be applied by more > companies as soon as possible -- This message was sent by Atlassian JIRA (v6.3.4#6332)
