[jira] [Commented] (TRAFODION-2163) support MYSQL style function GROUP_CONCAT
[ https://issues.apache.org/jira/browse/TRAFODION-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422012#comment-15422012 ] liu ming commented on TRAFODION-2163: - Hi, Anoop, Thanks for the valuable comments. I was trying to simulate GROUP_CONCAT, and then find out pivot_group already implemented. And basic functional test shows it works as expected. So I would like to first add MySQL style syntax sugar. And do more tests. We still just need it for limited use for now IMHO, to meet some basic requirements in some real use cases where people have to write code. And could you say more about 'issues related to parallel execution' ? Is there any specific error/issues description about that? So I can take a look and try to work on it. thanks, Ming > support MYSQL style function GROUP_CONCAT > - > > Key: TRAFODION-2163 > URL: https://issues.apache.org/jira/browse/TRAFODION-2163 > Project: Apache Trafodion > Issue Type: Sub-task >Reporter: liu ming >Assignee: liu ming > > One popular MySQL function is GROUP_CONCAT : > SELECT student_name, > GROUP_CONCAT(DISTINCT test_score > ORDER BY test_score asc SEPARATOR ' ') > FROM student > GROUP BY student_name; > Support this syntax. > This helps migration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2161) Metadata upgrade failed when there is user view on repository tables
[ https://issues.apache.org/jira/browse/TRAFODION-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421939#comment-15421939 ] David Wayne Birdsall commented on TRAFODION-2161: - Yes, by creating a view against the METRIC_QUERY_TABLE, I was able to reproduce this problem. I will next debug and fix it. > 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: David Wayne Birdsall > > [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] [Commented] (TRAFODION-2161) Metadata upgrade failed when there is user view on repository tables
[ https://issues.apache.org/jira/browse/TRAFODION-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421796#comment-15421796 ] David Wayne Birdsall commented on TRAFODION-2161: - On reflection, I think I know why my test succeeded (that is, why it failed to reproduce the problem). I was unwise in my choice of tables to reference. I happened to pick a repository table that didn't change in the upgrade. I will try again with a better test case. > 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: David Wayne Birdsall > > [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] [Commented] (TRAFODION-2161) Metadata upgrade failed when there is user view on repository tables
[ https://issues.apache.org/jira/browse/TRAFODION-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421779#comment-15421779 ] David Wayne Birdsall commented on TRAFODION-2161: - The person reporting the problem mentioned in a private e-mail that a view existed on one of the Repository tables (that is, a table in the "_REPOS_" schema). I just attempted to reproduce the problem on Trafodion by using an older pre-upgrade instance, creating a view on a Repository table, then rebuilding the instance as the latest Trafodion. Just for fun as part of the exercise, I created a view on a Metadata table as well. Upgrade worked fine. So this may be specific to the EsgynDB derived product. I will investigate that. > 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: David Wayne Birdsall > > [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-2161) Metadata upgrade failed when there is user view on repository tables
[ https://issues.apache.org/jira/browse/TRAFODION-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Wayne Birdsall reassigned TRAFODION-2161: --- Assignee: David Wayne Birdsall (was: Roberta Marton) > 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: David Wayne Birdsall > > [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-1562) Changes in query tree when the upsert command is transformed into merge
[ https://issues.apache.org/jira/browse/TRAFODION-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandhya Sundaresan reassigned TRAFODION-1562: - Assignee: Sandhya Sundaresan (was: Suresh Subbiah) > Changes in query tree when the upsert command is transformed into merge > --- > > Key: TRAFODION-1562 > URL: https://issues.apache.org/jira/browse/TRAFODION-1562 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: Selvaganesan Govindarajan >Assignee: Sandhya Sundaresan > Attachments: BatchUpsertTransformation.pdf > > > to improve the performance as explained in the main JIRA -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2162) Enhance showplan output to show the expr instruction being generated
[ https://issues.apache.org/jira/browse/TRAFODION-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421388#comment-15421388 ] ASF GitHub Bot commented on TRAFODION-2162: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/658 > Enhance showplan output to show the expr instruction being generated > > > Key: TRAFODION-2162 > URL: https://issues.apache.org/jira/browse/TRAFODION-2162 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: Anoop Sharma >Assignee: Anoop Sharma >Priority: Minor > > Currently, showplan doesnt show the instruction being generated > for the conversion, comparison, arith, etc expression. > This instruction is used at runtime to switch to the appropriate > case stmt which needs to be executed. > This enhancement is to display the actual case index that is being > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2162) Enhance showplan output to show the expr instruction being generated
[
https://issues.apache.org/jira/browse/TRAFODION-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421274#comment-15421274
]
ASF GitHub Bot commented on TRAFODION-2162:
---
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/658#discussion_r74794960
--- Diff: core/sql/exp/exp_clause.h ---
@@ -557,7 +563,11 @@ class SQLEXP_LIB_FUNC ex_clause : public
NAVersionedObject {
Int16 /*OperatorTypeEnum*/ operType_;// 34-35
Int16 /*clause_type*/ clauseType_; // 36-37
- Int16 filler1_; // 38-39
+ // index into static clause array struct containing details about
+ // this clause (datatypes, operation, etc) if derived clause has
+ // this array defined.
+ // See derived clauses for details.
+ Int16 instrArrayIndex_; // 48-49
--- End diff --
I assume the comment should read, 38-39?
> Enhance showplan output to show the expr instruction being generated
>
>
> Key: TRAFODION-2162
> URL: https://issues.apache.org/jira/browse/TRAFODION-2162
> Project: Apache Trafodion
> Issue Type: Improvement
>Reporter: Anoop Sharma
>Assignee: Anoop Sharma
>Priority: Minor
>
> Currently, showplan doesnt show the instruction being generated
> for the conversion, comparison, arith, etc expression.
> This instruction is used at runtime to switch to the appropriate
> case stmt which needs to be executed.
> This enhancement is to display the actual case index that is being
> generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1440) Ubuntu Support
[ https://issues.apache.org/jira/browse/TRAFODION-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran updated TRAFODION-1440: Assignee: (was: Amanda Moran) > Ubuntu Support > --- > > Key: TRAFODION-1440 > URL: https://issues.apache.org/jira/browse/TRAFODION-1440 > Project: Apache Trafodion > Issue Type: New Feature > Components: installer >Reporter: Amanda Moran > > Ubuntu support for Installer and any core components if needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2154) Document IF [NOT] EXISTS for CREATE/DROP SCHEMA
[ https://issues.apache.org/jira/browse/TRAFODION-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Wayne Birdsall resolved TRAFODION-2154. - Resolution: Fixed Web site rebuilt just now. > Document IF [NOT] EXISTS for CREATE/DROP SCHEMA > --- > > Key: TRAFODION-2154 > URL: https://issues.apache.org/jira/browse/TRAFODION-2154 > Project: Apache Trafodion > Issue Type: Documentation > Components: documentation >Affects Versions: any > Environment: All >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall >Priority: Minor > Fix For: 2.1-incubating > > > The IF NOT EXISTS option is not documented for CREATE SCHEMA. The IF EXISTS > option is not documented for DROP SCHEMA. We should add those. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2164) Document Incremental Update Statistics syntax
David Wayne Birdsall created TRAFODION-2164: --- Summary: Document Incremental Update Statistics syntax Key: TRAFODION-2164 URL: https://issues.apache.org/jira/browse/TRAFODION-2164 Project: Apache Trafodion Issue Type: Improvement Components: sql-cmp Affects Versions: 2.1-incubating Environment: All Reporter: David Wayne Birdsall Assignee: David Wayne Birdsall Recently, incremental update statistics functionality was added to Trafodion. The SQL reference manual needs to be updated with this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2163) support MYSQL style function GROUP_CONCAT
[ https://issues.apache.org/jira/browse/TRAFODION-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421100#comment-15421100 ] liu ming commented on TRAFODION-2163: - reuse pivot_group > support MYSQL style function GROUP_CONCAT > - > > Key: TRAFODION-2163 > URL: https://issues.apache.org/jira/browse/TRAFODION-2163 > Project: Apache Trafodion > Issue Type: Sub-task >Reporter: liu ming >Assignee: liu ming > > One popular MySQL function is GROUP_CONCAT : > SELECT student_name, > GROUP_CONCAT(DISTINCT test_score > ORDER BY test_score asc SEPARATOR ' ') > FROM student > GROUP BY student_name; > Support this syntax. > This helps migration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2163) support MYSQL style function GROUP_CONCAT
[ https://issues.apache.org/jira/browse/TRAFODION-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2163 started by liu ming. --- > support MYSQL style function GROUP_CONCAT > - > > Key: TRAFODION-2163 > URL: https://issues.apache.org/jira/browse/TRAFODION-2163 > Project: Apache Trafodion > Issue Type: Sub-task >Reporter: liu ming >Assignee: liu ming > > One popular MySQL function is GROUP_CONCAT : > SELECT student_name, > GROUP_CONCAT(DISTINCT test_score > ORDER BY test_score asc SEPARATOR ' ') > FROM student > GROUP BY student_name; > Support this syntax. > This helps migration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2163) support MYSQL style function GROUP_CONCAT
[ https://issues.apache.org/jira/browse/TRAFODION-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2163: --- Assignee: liu ming > support MYSQL style function GROUP_CONCAT > - > > Key: TRAFODION-2163 > URL: https://issues.apache.org/jira/browse/TRAFODION-2163 > Project: Apache Trafodion > Issue Type: Sub-task >Reporter: liu ming >Assignee: liu ming > > One popular MySQL function is GROUP_CONCAT : > SELECT student_name, > GROUP_CONCAT(DISTINCT test_score > ORDER BY test_score asc SEPARATOR ' ') > FROM student > GROUP BY student_name; > Support this syntax. > This helps migration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2163) support MYSQL style function GROUP_CONCAT
liu ming created TRAFODION-2163: --- Summary: support MYSQL style function GROUP_CONCAT Key: TRAFODION-2163 URL: https://issues.apache.org/jira/browse/TRAFODION-2163 Project: Apache Trafodion Issue Type: Sub-task Reporter: liu ming One popular MySQL function is GROUP_CONCAT : SELECT student_name, GROUP_CONCAT(DISTINCT test_score ORDER BY test_score asc SEPARATOR ' ') FROM student GROUP BY student_name; Support this syntax. This helps migration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
