[jira] [Assigned] (TRAFODION-2090) improve the very first time of query compiling
[ https://issues.apache.org/jira/browse/TRAFODION-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2090: --- Assignee: liu ming > improve the very first time of query compiling > -- > > Key: TRAFODION-2090 > URL: https://issues.apache.org/jira/browse/TRAFODION-2090 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: liu ming > > Currently, the very first query run in master executor: sqlci or mxosrvr will > take seconds to compile. > Initial analysis shows most time spend on metadata retrieving. > Need to improve the compile time for the very first time, at least from end > user's perspective. > Speed up the metadata retrieval speed. > Redesign metadata scheme > Prefetch metadata > are all among possible solutions, the aim is to shorten the time spend on the > SQL compile for the first time. Initial goal is within 1 second, faster the > better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1986) trafodion jdbc t4 api can't set schema
[
https://issues.apache.org/jira/browse/TRAFODION-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liu ming updated TRAFODION-1986:
Assignee: mashengchen (was: liu ming)
> trafodion jdbc t4 api can't set schema
> --
>
> Key: TRAFODION-1986
> URL: https://issues.apache.org/jira/browse/TRAFODION-1986
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: mashengchen
>Assignee: mashengchen
>
> connection.setSchema(string schemaName) doesn't work.
>
> connection.setSchema("_REPOS_");
> System.out.println(connection.getSchema());
> ---
> the output is still "SEABASE"
> the source code seems doesn't implement
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-2133) support Hive native data type CHAR
liu ming created TRAFODION-2133:
---
Summary: support Hive native data type CHAR
Key: TRAFODION-2133
URL: https://issues.apache.org/jira/browse/TRAFODION-2133
Project: Apache Trafodion
Issue Type: Sub-task
Components: sql-cmp, sql-general
Reporter: liu ming
This JIRA is not too complex, so a good beginner's JIRA.
support CHAR data type from Hive DDL.
create table tbl_char
{
c1 char(10),
c2 char(20)
};
in hive, and insert some value, it should be able to read from Trafodion via
sqlci:
select * from hive.hive.tbl_char
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-2047) add SQL syntax support to INTERSECT
[ https://issues.apache.org/jira/browse/TRAFODION-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2047: Fix Version/s: 2.1-incubating > add SQL syntax support to INTERSECT > --- > > Key: TRAFODION-2047 > URL: https://issues.apache.org/jira/browse/TRAFODION-2047 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > INTERSECT is a common SQL syntax. > Trafodion should support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1673. - Resolution: Fixed initial support is done, enhancement will be done in iterations. > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > Fix For: 2.1-incubating > > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2127) enhance Trafodion implementation of WITH clause
liu ming created TRAFODION-2127: --- Summary: enhance Trafodion implementation of WITH clause Key: TRAFODION-2127 URL: https://issues.apache.org/jira/browse/TRAFODION-2127 Project: Apache Trafodion Issue Type: Improvement Reporter: liu ming TRAFODION-1673 described some details about how to support WITH clause in Trafodion. As initial implementation, we use a simple pure-parser method. That way, Trafodion can support WITH clause functionally, but not good from performance point of view, also need to enhance the parser to be more strict in syntax. This JIRA is a follow up JIRA, to track following effort to support Trafodion WITH clause. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1538) Trafodion external tables not dropped when native HBase table is dropped.
[ https://issues.apache.org/jira/browse/TRAFODION-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1538: Fix Version/s: 2.1-incubating > Trafodion external tables not dropped when native HBase table is dropped. > - > > Key: TRAFODION-1538 > URL: https://issues.apache.org/jira/browse/TRAFODION-1538 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmu >Reporter: Roberta Marton >Assignee: liu ming > Fix For: 2.1-incubating > > > In order to perform SQL operations on native tables, special Trafodion > external tables are created to match the associated native tables. When an > HBase native table is dropped, the corresponding Trafodion external table > should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1538) Trafodion external tables not dropped when native HBase table is dropped.
[ https://issues.apache.org/jira/browse/TRAFODION-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1538. - Resolution: Cannot Reproduce probably fixed by other changes. > Trafodion external tables not dropped when native HBase table is dropped. > - > > Key: TRAFODION-1538 > URL: https://issues.apache.org/jira/browse/TRAFODION-1538 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmu >Reporter: Roberta Marton >Assignee: liu ming > > In order to perform SQL operations on native tables, special Trafodion > external tables are created to match the associated native tables. When an > HBase native table is dropped, the corresponding Trafodion external table > should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1868) Compatibility with gcc 4.8
[ https://issues.apache.org/jira/browse/TRAFODION-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390960#comment-15390960 ] liu ming commented on TRAFODION-1868: - yes, SQL errors was not checked in yet. I will start to work on this again asap. We already have all fixes, but not merge into main branch yet. > Compatibility with gcc 4.8 > -- > > Key: TRAFODION-1868 > URL: https://issues.apache.org/jira/browse/TRAFODION-1868 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau >Assignee: liu ming >Priority: Minor > > Current code will not compile with gcc 4.8. That is the default version on > RH/CentOS 7. This is needed to move to a development environment on CentOS 7. > There is a 4.4 version of gcc available on 7. The RPM package is > compat-gcc-44, I have not tried building on 7.x with older compiler, but will > likely work. > This is not urgent at this time, but we should move toward enabling a newer > dev environment. But this needs to be coordinated with with versions of OS > are supported for runtime use of trafodion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2121 started by liu ming. --- > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1868) Compatibility with gcc 4.8
[ https://issues.apache.org/jira/browse/TRAFODION-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1868: Assignee: Arvind Narain (was: liu ming) > Compatibility with gcc 4.8 > -- > > Key: TRAFODION-1868 > URL: https://issues.apache.org/jira/browse/TRAFODION-1868 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau >Assignee: Arvind Narain >Priority: Minor > > Current code will not compile with gcc 4.8. That is the default version on > RH/CentOS 7. This is needed to move to a development environment on CentOS 7. > There is a 4.4 version of gcc available on 7. The RPM package is > compat-gcc-44, I have not tried building on 7.x with older compiler, but will > likely work. > This is not urgent at this time, but we should move toward enabling a newer > dev environment. But this needs to be coordinated with with versions of OS > are supported for runtime use of trafodion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2133) support Hive native data type CHAR
[
https://issues.apache.org/jira/browse/TRAFODION-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399299#comment-15399299
]
liu ming commented on TRAFODION-2133:
-
This is a good JIRA candidate for beginners.
> support Hive native data type CHAR
> --
>
> Key: TRAFODION-2133
> URL: https://issues.apache.org/jira/browse/TRAFODION-2133
> Project: Apache Trafodion
> Issue Type: Sub-task
> Components: sql-cmp, sql-general
>Reporter: liu ming
> Labels: newbie
>
> This JIRA is not too complex, so a good beginner's JIRA.
> support CHAR data type from Hive DDL.
> create table tbl_char
> {
> c1 char(10),
> c2 char(20)
> };
> in hive, and insert some value, it should be able to read from Trafodion via
> sqlci:
> select * from hive.hive.tbl_char
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1874) find a new way to check CLUSTER environment instead of checking pdsh
[ https://issues.apache.org/jira/browse/TRAFODION-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1874. - Resolution: Fixed Fix Version/s: 2.1-incubating > find a new way to check CLUSTER environment instead of checking pdsh > > > Key: TRAFODION-1874 > URL: https://issues.apache.org/jira/browse/TRAFODION-1874 > Project: Apache Trafodion > Issue Type: Improvement > Components: foundation, installer >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > Some Trafodion script need to tell if it is running in a dev workstation or a > real cluster, and behave differently. > Current, some script tell this difference by checking the rpm package pdsh, > if it is installed, then the script think it is running on a cluster. > PDSH is a public package, and can be installed in a workstation as well. So > it is better to find a new testing logic for this purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1874) find a new way to check CLUSTER environment instead of checking pdsh
[ https://issues.apache.org/jira/browse/TRAFODION-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399570#comment-15399570 ] liu ming commented on TRAFODION-1874: - I cannot find scripts checking PDSH for cluster now. So close this JIRA. > find a new way to check CLUSTER environment instead of checking pdsh > > > Key: TRAFODION-1874 > URL: https://issues.apache.org/jira/browse/TRAFODION-1874 > Project: Apache Trafodion > Issue Type: Improvement > Components: foundation, installer >Reporter: liu ming >Assignee: liu ming > > Some Trafodion script need to tell if it is running in a dev workstation or a > real cluster, and behave differently. > Current, some script tell this difference by checking the rpm package pdsh, > if it is installed, then the script think it is running on a cluster. > PDSH is a public package, and can be installed in a workstation as well. So > it is better to find a new testing logic for this purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
[ https://issues.apache.org/jira/browse/TRAFODION-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400729#comment-15400729 ] liu ming commented on TRAFODION-2119: - A simpler reproduce test: cqd allow_nullable_unique_key_constraint 'on' ; drop table t1s; create table t1s (c1 char(12) character set utf8 , c2 char(8) character set utf8 ) store by (c1) salt using 4 partitions on (c1) ; The issue is in CharType method of minMaxRepresentableValue() which ignore the null byte. > create table report strange WARNING when using store by and > allow_nullable_unique_key_constraint CQD > > > Key: TRAFODION-2119 > URL: https://issues.apache.org/jira/browse/TRAFODION-2119 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > cqd allow_nullable_unique_key_constraint 'on' ; > create table T_RH_DZSP > ( > s_orgcode CHAR(12) character set utf8, > s_applydate CHAR(8) character set utf8, > s_packnovarchar(8) character set utf8, > s_trecode CHAR(10) character set utf8, > s_trename varchar(60) character set utf8, > s_taxorgcodevarchar(12) character set utf8, > s_paybnkno varchar(12) character set utf8, > s_trano varchar(8) character set utf8, > s_orimsgno CHAR(4) character set utf8, > f_traamtnumeric(18,2), > s_payeropnbnkno varchar(12) character set utf8, > payeropbkname varchar(60) character set utf8, > s_handorgname varchar(200) character set utf8, > s_payacct varchar(32) character set utf8, > s_taxvouno varchar(20) character set utf8, > s_billdate CHAR(8) character set utf8, > s_taxpaycodevarchar(20) character set utf8, > s_taxpaynamevarchar(200) character set utf8, > c_budgettypeCHAR(1) character set utf8, > c_trimflag CHAR(1) character set utf8, > s_etpcode varchar(20) character set utf8, > s_etpname varchar(200) character set utf8, > s_etptype varchar(20) character set utf8, > s_bdgsbtcodevarchar(30) character set utf8, > s_bdgsbtnamevarchar(60) character set utf8, > s_limit CHAR(8) character set utf8, > s_taxtypecode CHAR(10) character set utf8, > s_taxkindname varchar(60) character set utf8, > c_bdglevel CHAR(1) character set utf8, > c_bdglevelname varchar(60) character set utf8, > s_taxstartdate CHAR(8) character set utf8, > s_taxenddateCHAR(8) character set utf8, > s_astflag varchar(35) character set utf8, > c_taxtype CHAR(1) character set utf8, > s_acct CHAR(8) character set utf8, > s_trastate CHAR(2) character set utf8, > s_remarkvarchar(60) character set utf8, > s_remark1 varchar(60) character set utf8, > s_remark2 varchar(60) character set utf8, > s_inputerid varchar(18) character set utf8, > ts_sysupdatevarchar(100) character set utf8, > s_seq varchar(100) character set utf8 > ) > store by (S_APPLYDATE) > salt using 48 partitions on (S_APPLYDATE) > ATTRIBUTES ALIGNED FORMAT > HBASE_OPTIONS > ( > DATA_BLOCK_ENCODING = 'FAST_DIFF', > -- COMPRESSION = 'SNAPPY', > MEMSTORE_FLUSH_SIZE = '1073741824' > ); > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of
[jira] [Updated] (TRAFODION-1744) Session user information is incorrect in stored procedures
[ https://issues.apache.org/jira/browse/TRAFODION-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1744: Assignee: mashengchen (was: liu ming) > Session user information is incorrect in stored procedures > -- > > Key: TRAFODION-1744 > URL: https://issues.apache.org/jira/browse/TRAFODION-1744 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Reporter: Roberta Marton >Assignee: mashengchen > > If I run a stored procedure in a sqlci session and connect as a user other > than DB__ROOT, I expected that user identification to be sent to the stored > procedure. However, the user id is always DB__ROOT. > As db__root. > create a procedure. Include the SQL command: values(user); > grant execute on procedure to sql_user1 > As sql_user > sqlci -u sql_user1; > >> values (user); > (EXPR) > --- > SQL_USER1 > call the store procedure and see that the embedded values command returns > DB__ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
[ https://issues.apache.org/jira/browse/TRAFODION-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2119 started by liu ming. --- > create table report strange WARNING when using store by and > allow_nullable_unique_key_constraint CQD > > > Key: TRAFODION-2119 > URL: https://issues.apache.org/jira/browse/TRAFODION-2119 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > cqd allow_nullable_unique_key_constraint 'on' ; > create table T_RH_DZSP > ( > s_orgcode CHAR(12) character set utf8, > s_applydate CHAR(8) character set utf8, > s_packnovarchar(8) character set utf8, > s_trecode CHAR(10) character set utf8, > s_trename varchar(60) character set utf8, > s_taxorgcodevarchar(12) character set utf8, > s_paybnkno varchar(12) character set utf8, > s_trano varchar(8) character set utf8, > s_orimsgno CHAR(4) character set utf8, > f_traamtnumeric(18,2), > s_payeropnbnkno varchar(12) character set utf8, > payeropbkname varchar(60) character set utf8, > s_handorgname varchar(200) character set utf8, > s_payacct varchar(32) character set utf8, > s_taxvouno varchar(20) character set utf8, > s_billdate CHAR(8) character set utf8, > s_taxpaycodevarchar(20) character set utf8, > s_taxpaynamevarchar(200) character set utf8, > c_budgettypeCHAR(1) character set utf8, > c_trimflag CHAR(1) character set utf8, > s_etpcode varchar(20) character set utf8, > s_etpname varchar(200) character set utf8, > s_etptype varchar(20) character set utf8, > s_bdgsbtcodevarchar(30) character set utf8, > s_bdgsbtnamevarchar(60) character set utf8, > s_limit CHAR(8) character set utf8, > s_taxtypecode CHAR(10) character set utf8, > s_taxkindname varchar(60) character set utf8, > c_bdglevel CHAR(1) character set utf8, > c_bdglevelname varchar(60) character set utf8, > s_taxstartdate CHAR(8) character set utf8, > s_taxenddateCHAR(8) character set utf8, > s_astflag varchar(35) character set utf8, > c_taxtype CHAR(1) character set utf8, > s_acct CHAR(8) character set utf8, > s_trastate CHAR(2) character set utf8, > s_remarkvarchar(60) character set utf8, > s_remark1 varchar(60) character set utf8, > s_remark2 varchar(60) character set utf8, > s_inputerid varchar(18) character set utf8, > ts_sysupdatevarchar(100) character set utf8, > s_seq varchar(100) character set utf8 > ) > store by (S_APPLYDATE) > salt using 48 partitions on (S_APPLYDATE) > ATTRIBUTES ALIGNED FORMAT > HBASE_OPTIONS > ( > DATA_BLOCK_ENCODING = 'FAST_DIFF', > -- COMPRESSION = 'SNAPPY', > MEMSTORE_FLUSH_SIZE = '1073741824' > ); > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > ***
[jira] [Commented] (TRAFODION-1909) Output of showddl differs from output of jdbc client (t4)
[
https://issues.apache.org/jira/browse/TRAFODION-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401229#comment-15401229
]
liu ming commented on TRAFODION-1909:
-
test with JDBC T4 program and data type works fine, sample code:
Class.forName("org.trafodion.jdbc.t4.T4Driver");
Connection conn =
DriverManager.getConnection("jdbc:t4jdbc://10.10.10.8:23400/:", "usr", "pwd");
Statement stmt = conn.createStatement();
targetTable = "t1";
String line = "select * from " + targetTable;
rs = stmt.executeQuery(line);
ResultSetMetaData md = rs.getMetaData() ;
for( int i = 1; i <= md.getColumnCount(); i++ )
{
System.out.print( md.getColumnLabel(i) + " " ) ;
System.out.print( md.getColumnTypeName(i) + "
");
System.out.print( md.getPrecision(i) + " ");
System.out.print( md.isNullable(i) + " ");
System.out.print( md.getColumnClassName(i) + "
");
}
rs.close() ;
So probably already fixed issue.
> Output of showddl differs from output of jdbc client (t4)
> -
>
> Key: TRAFODION-1909
> URL: https://issues.apache.org/jira/browse/TRAFODION-1909
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t4
>Affects Versions: 1.3-incubating
>Reporter: Pierre Smits
>Assignee: liu ming
>
> as per thread on the dev ml. See http://markmail.org/message/tw73lpq3k3fkldvr
> This is returned in the application (Apache OFBiz)
> {code}
> Column [ESTIMATED_COST] of table [OFBIZ.WORK_EFFORT_GOOD_STANDARD] of
> entity [WorkEffortGoodStandard] is of type [BIGINT] in the database, but is
> defined as type [NUMERIC] in the entity definition.
> {code}
> This is returned with the showddl command;
> {code}>>showddl table OFBIZ.WORK_EFFORT_GOOD_STANDARD;
>CREATE TABLE TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , PRODUCT_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , WORK_EFFORT_GOOD_STD_TYPE_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , FROM_DATETIMESTAMP(6) NO DEFAULT NOT NULL NOT
> DROPPABLE NOT SERIALIZED
> , THRU_DATETIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , STATUS_IDVARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT DEFAULT NULL SERIALIZED
> , ESTIMATED_QUANTITY DOUBLE PRECISION DEFAULT NULL NOT
> SERIALIZED
> , ESTIMATED_COST NUMERIC(18, 2) DEFAULT NULL
>SERIALIZED
> , LAST_UPDATED_STAMP TIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , LAST_UPDATED_TX_STAMPTIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , CREATED_STAMPTIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , CREATED_TX_STAMP TIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , PRIMARY KEY (WORK_EFFORT_ID ASC, PRODUCT_ID ASC,
>WORK_EFFORT_GOOD_STD_TYPE_ID ASC, FROM_DATE ASC)
> )
>;
>CREATE INDEX WKEFF_GDSTD_PROD ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>PRODUCT_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_STTS ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>STATUS_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_TYPE ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_GOOD_STD_TYPE_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_WEFF ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_ID ASC
> )
>;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1909) Output of showddl differs from output of jdbc client (t4)
[
https://issues.apache.org/jira/browse/TRAFODION-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liu ming resolved TRAFODION-1909.
-
Resolution: Cannot Reproduce
> Output of showddl differs from output of jdbc client (t4)
> -
>
> Key: TRAFODION-1909
> URL: https://issues.apache.org/jira/browse/TRAFODION-1909
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t4
>Affects Versions: 1.3-incubating
>Reporter: Pierre Smits
>Assignee: liu ming
>
> as per thread on the dev ml. See http://markmail.org/message/tw73lpq3k3fkldvr
> This is returned in the application (Apache OFBiz)
> {code}
> Column [ESTIMATED_COST] of table [OFBIZ.WORK_EFFORT_GOOD_STANDARD] of
> entity [WorkEffortGoodStandard] is of type [BIGINT] in the database, but is
> defined as type [NUMERIC] in the entity definition.
> {code}
> This is returned with the showddl command;
> {code}>>showddl table OFBIZ.WORK_EFFORT_GOOD_STANDARD;
>CREATE TABLE TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , PRODUCT_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , WORK_EFFORT_GOOD_STD_TYPE_ID VARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
> , FROM_DATETIMESTAMP(6) NO DEFAULT NOT NULL NOT
> DROPPABLE NOT SERIALIZED
> , THRU_DATETIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , STATUS_IDVARCHAR(20) CHARACTER SET ISO88591
>COLLATE
> DEFAULT DEFAULT NULL SERIALIZED
> , ESTIMATED_QUANTITY DOUBLE PRECISION DEFAULT NULL NOT
> SERIALIZED
> , ESTIMATED_COST NUMERIC(18, 2) DEFAULT NULL
>SERIALIZED
> , LAST_UPDATED_STAMP TIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , LAST_UPDATED_TX_STAMPTIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , CREATED_STAMPTIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , CREATED_TX_STAMP TIMESTAMP(6) DEFAULT NULL NOT
>SERIALIZED
> , PRIMARY KEY (WORK_EFFORT_ID ASC, PRODUCT_ID ASC,
>WORK_EFFORT_GOOD_STD_TYPE_ID ASC, FROM_DATE ASC)
> )
>;
>CREATE INDEX WKEFF_GDSTD_PROD ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>PRODUCT_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_STTS ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>STATUS_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_TYPE ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_GOOD_STD_TYPE_ID ASC
> )
>;
>CREATE INDEX WKEFF_GDSTD_WEFF ON
>TRAFODION.OFBIZ.WORK_EFFORT_GOOD_STANDARD
> (
>WORK_EFFORT_ID ASC
> )
>;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2121. - Resolution: Fixed Fix Version/s: 2.1-incubating > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2047) add SQL syntax support to INTERSECT
[ https://issues.apache.org/jira/browse/TRAFODION-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2047. - Resolution: Fixed > add SQL syntax support to INTERSECT > --- > > Key: TRAFODION-2047 > URL: https://issues.apache.org/jira/browse/TRAFODION-2047 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > INTERSECT is a common SQL syntax. > Trafodion should support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2117) add support of SQL extension 'EXCEPT'
[ https://issues.apache.org/jira/browse/TRAFODION-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2117 started by liu ming. --- > add support of SQL extension 'EXCEPT' > -- > > Key: TRAFODION-2117 > URL: https://issues.apache.org/jira/browse/TRAFODION-2117 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > > add syntax and basic functional support for 'EXCEPT', meet the requirement to > run TPCDS as initial goal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work stopped] (TRAFODION-2090) improve the very first time of query compiling
[ https://issues.apache.org/jira/browse/TRAFODION-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2090 stopped by liu ming. --- > improve the very first time of query compiling > -- > > Key: TRAFODION-2090 > URL: https://issues.apache.org/jira/browse/TRAFODION-2090 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > Currently, the very first query run in master executor: sqlci or mxosrvr will > take seconds to compile. > Initial analysis shows most time spend on metadata retrieving. > Need to improve the compile time for the very first time, at least from end > user's perspective. > Speed up the metadata retrieval speed. > Redesign metadata scheme > Prefetch metadata > are all among possible solutions, the aim is to shorten the time spend on the > SQL compile for the first time. Initial goal is within 1 second, faster the > better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2090) improve the very first time of query compiling
[ https://issues.apache.org/jira/browse/TRAFODION-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2090. - Resolution: Duplicate Fix Version/s: 2.1-incubating duplicated TRAFODION-2137 > improve the very first time of query compiling > -- > > Key: TRAFODION-2090 > URL: https://issues.apache.org/jira/browse/TRAFODION-2090 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > Currently, the very first query run in master executor: sqlci or mxosrvr will > take seconds to compile. > Initial analysis shows most time spend on metadata retrieving. > Need to improve the compile time for the very first time, at least from end > user's perspective. > Speed up the metadata retrieval speed. > Redesign metadata scheme > Prefetch metadata > are all among possible solutions, the aim is to shorten the time spend on the > SQL compile for the first time. Initial goal is within 1 second, faster the > better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1701) Handle duplicate rows in ODBC/JDBC batch inserts
[ https://issues.apache.org/jira/browse/TRAFODION-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1701: Assignee: mashengchen (was: liu ming) > Handle duplicate rows in ODBC/JDBC batch inserts > > > Key: TRAFODION-1701 > URL: https://issues.apache.org/jira/browse/TRAFODION-1701 > Project: Apache Trafodion > Issue Type: Improvement >Affects Versions: 1.1 (pre-incubation) > Environment: Any, using ODBC or JDBC batch inserts >Reporter: Hans Zeller >Assignee: mashengchen > > See test > tests/phx/src/test/java/org/trafodion/phoenix/end2end/BatchTest.java. It has > the code that checks the result after a batch insert with duplicates > commented out. The fix would make this test pass with the checks uncommented. -- 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] [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] [Resolved] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
[ https://issues.apache.org/jira/browse/TRAFODION-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2119. - Resolution: Fixed Fix Version/s: 2.1-incubating > create table report strange WARNING when using store by and > allow_nullable_unique_key_constraint CQD > > > Key: TRAFODION-2119 > URL: https://issues.apache.org/jira/browse/TRAFODION-2119 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > cqd allow_nullable_unique_key_constraint 'on' ; > create table T_RH_DZSP > ( > s_orgcode CHAR(12) character set utf8, > s_applydate CHAR(8) character set utf8, > s_packnovarchar(8) character set utf8, > s_trecode CHAR(10) character set utf8, > s_trename varchar(60) character set utf8, > s_taxorgcodevarchar(12) character set utf8, > s_paybnkno varchar(12) character set utf8, > s_trano varchar(8) character set utf8, > s_orimsgno CHAR(4) character set utf8, > f_traamtnumeric(18,2), > s_payeropnbnkno varchar(12) character set utf8, > payeropbkname varchar(60) character set utf8, > s_handorgname varchar(200) character set utf8, > s_payacct varchar(32) character set utf8, > s_taxvouno varchar(20) character set utf8, > s_billdate CHAR(8) character set utf8, > s_taxpaycodevarchar(20) character set utf8, > s_taxpaynamevarchar(200) character set utf8, > c_budgettypeCHAR(1) character set utf8, > c_trimflag CHAR(1) character set utf8, > s_etpcode varchar(20) character set utf8, > s_etpname varchar(200) character set utf8, > s_etptype varchar(20) character set utf8, > s_bdgsbtcodevarchar(30) character set utf8, > s_bdgsbtnamevarchar(60) character set utf8, > s_limit CHAR(8) character set utf8, > s_taxtypecode CHAR(10) character set utf8, > s_taxkindname varchar(60) character set utf8, > c_bdglevel CHAR(1) character set utf8, > c_bdglevelname varchar(60) character set utf8, > s_taxstartdate CHAR(8) character set utf8, > s_taxenddateCHAR(8) character set utf8, > s_astflag varchar(35) character set utf8, > c_taxtype CHAR(1) character set utf8, > s_acct CHAR(8) character set utf8, > s_trastate CHAR(2) character set utf8, > s_remarkvarchar(60) character set utf8, > s_remark1 varchar(60) character set utf8, > s_remark2 varchar(60) character set utf8, > s_inputerid varchar(18) character set utf8, > ts_sysupdatevarchar(100) character set utf8, > s_seq varchar(100) character set utf8 > ) > store by (S_APPLYDATE) > salt using 48 partitions on (S_APPLYDATE) > ATTRIBUTES ALIGNED FORMAT > HBASE_OPTIONS > ( > DATA_BLOCK_ENCODING = 'FAST_DIFF', > -- COMPRESSION = 'SNAPPY', > MEMSTORE_FLUSH_SIZE = '1073741824' > ); > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string
[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] [Resolved] (TRAFODION-2096) create all tpcds hive external tables from install_local_hadoop
[ https://issues.apache.org/jira/browse/TRAFODION-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2096. - Resolution: Fixed Fix Version/s: 2.1-incubating > create all tpcds hive external tables from install_local_hadoop > --- > > Key: TRAFODION-2096 > URL: https://issues.apache.org/jira/browse/TRAFODION-2096 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: liu ming >Priority: Minor > Fix For: 2.1-incubating > > > store_returns > catalog_sales > catalog_returns > web_sales > web_returns > inventory > call_center > catalog_page > web_site > Web_page > warehouse > income_band > reason > ship_mode > These tables were used by TPCDS queries, it will help to automatically > install them in a dev environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
[ https://issues.apache.org/jira/browse/TRAFODION-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2119: --- Assignee: liu ming > create table report strange WARNING when using store by and > allow_nullable_unique_key_constraint CQD > > > Key: TRAFODION-2119 > URL: https://issues.apache.org/jira/browse/TRAFODION-2119 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > cqd allow_nullable_unique_key_constraint 'on' ; > create table T_RH_DZSP > ( > s_orgcode CHAR(12) character set utf8, > s_applydate CHAR(8) character set utf8, > s_packnovarchar(8) character set utf8, > s_trecode CHAR(10) character set utf8, > s_trename varchar(60) character set utf8, > s_taxorgcodevarchar(12) character set utf8, > s_paybnkno varchar(12) character set utf8, > s_trano varchar(8) character set utf8, > s_orimsgno CHAR(4) character set utf8, > f_traamtnumeric(18,2), > s_payeropnbnkno varchar(12) character set utf8, > payeropbkname varchar(60) character set utf8, > s_handorgname varchar(200) character set utf8, > s_payacct varchar(32) character set utf8, > s_taxvouno varchar(20) character set utf8, > s_billdate CHAR(8) character set utf8, > s_taxpaycodevarchar(20) character set utf8, > s_taxpaynamevarchar(200) character set utf8, > c_budgettypeCHAR(1) character set utf8, > c_trimflag CHAR(1) character set utf8, > s_etpcode varchar(20) character set utf8, > s_etpname varchar(200) character set utf8, > s_etptype varchar(20) character set utf8, > s_bdgsbtcodevarchar(30) character set utf8, > s_bdgsbtnamevarchar(60) character set utf8, > s_limit CHAR(8) character set utf8, > s_taxtypecode CHAR(10) character set utf8, > s_taxkindname varchar(60) character set utf8, > c_bdglevel CHAR(1) character set utf8, > c_bdglevelname varchar(60) character set utf8, > s_taxstartdate CHAR(8) character set utf8, > s_taxenddateCHAR(8) character set utf8, > s_astflag varchar(35) character set utf8, > c_taxtype CHAR(1) character set utf8, > s_acct CHAR(8) character set utf8, > s_trastate CHAR(2) character set utf8, > s_remarkvarchar(60) character set utf8, > s_remark1 varchar(60) character set utf8, > s_remark2 varchar(60) character set utf8, > s_inputerid varchar(18) character set utf8, > ts_sysupdatevarchar(100) character set utf8, > s_seq varchar(100) character set utf8 > ) > store by (S_APPLYDATE) > salt using 48 partitions on (S_APPLYDATE) > ATTRIBUTES ALIGNED FORMAT > HBASE_OPTIONS > ( > DATA_BLOCK_ENCODING = 'FAST_DIFF', > -- COMPRESSION = 'SNAPPY', > MEMSTORE_FLUSH_SIZE = '1073741824' > ); > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. >
[jira] [Created] (TRAFODION-2121) add support of HIVE data type of DECIMAL
liu ming created TRAFODION-2121: --- Summary: add support of HIVE data type of DECIMAL Key: TRAFODION-2121 URL: https://issues.apache.org/jira/browse/TRAFODION-2121 Project: Apache Trafodion Issue Type: Sub-task Reporter: liu ming support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2121: --- Assignee: liu ming > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
liu ming created TRAFODION-2119: --- Summary: create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD Key: TRAFODION-2119 URL: https://issues.apache.org/jira/browse/TRAFODION-2119 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming cqd allow_nullable_unique_key_constraint 'on' ; create table T_RH_DZSP ( s_orgcode CHAR(12) character set utf8, s_applydate CHAR(8) character set utf8, s_packnovarchar(8) character set utf8, s_trecode CHAR(10) character set utf8, s_trename varchar(60) character set utf8, s_taxorgcodevarchar(12) character set utf8, s_paybnkno varchar(12) character set utf8, s_trano varchar(8) character set utf8, s_orimsgno CHAR(4) character set utf8, f_traamtnumeric(18,2), s_payeropnbnkno varchar(12) character set utf8, payeropbkname varchar(60) character set utf8, s_handorgname varchar(200) character set utf8, s_payacct varchar(32) character set utf8, s_taxvouno varchar(20) character set utf8, s_billdate CHAR(8) character set utf8, s_taxpaycodevarchar(20) character set utf8, s_taxpaynamevarchar(200) character set utf8, c_budgettypeCHAR(1) character set utf8, c_trimflag CHAR(1) character set utf8, s_etpcode varchar(20) character set utf8, s_etpname varchar(200) character set utf8, s_etptype varchar(20) character set utf8, s_bdgsbtcodevarchar(30) character set utf8, s_bdgsbtnamevarchar(60) character set utf8, s_limit CHAR(8) character set utf8, s_taxtypecode CHAR(10) character set utf8, s_taxkindname varchar(60) character set utf8, c_bdglevel CHAR(1) character set utf8, c_bdglevelname varchar(60) character set utf8, s_taxstartdate CHAR(8) character set utf8, s_taxenddateCHAR(8) character set utf8, s_astflag varchar(35) character set utf8, c_taxtype CHAR(1) character set utf8, s_acct CHAR(8) character set utf8, s_trastate CHAR(2) character set utf8, s_remarkvarchar(60) character set utf8, s_remark1 varchar(60) character set utf8, s_remark2 varchar(60) character set utf8, s_inputerid varchar(18) character set utf8, ts_sysupdatevarchar(100) character set utf8, s_seq varchar(100) character set utf8 ) store by (S_APPLYDATE) salt using 48 partitions on (S_APPLYDATE) ATTRIBUTES ALIGNED FORMAT HBASE_OPTIONS ( DATA_BLOCK_ENCODING = 'FAST_DIFF', -- COMPRESSION = 'SNAPPY', MEMSTORE_FLUSH_SIZE = '1073741824' ); *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation
[jira] [Updated] (TRAFODION-2033) Can't use symbol " as separator in windows
[ https://issues.apache.org/jira/browse/TRAFODION-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2033: Assignee: zhangliang (was: liu ming) > Can't use symbol " as separator in windows > --- > > Key: TRAFODION-2033 > URL: https://issues.apache.org/jira/browse/TRAFODION-2033 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-odb > Environment: centos 6.7 HBase 1.0.0-cdh5.4.8 > odb.exe on windows 7-64 bits >Reporter: zhangliang >Assignee: zhangliang >Priority: Minor > > Most of us are used to use " as the separator of strings, while " or ^" is > not available for odb.exe parameter fs and sq on windows. > Besides, it's better to update some information about what kinds of symbles > can be used as fs and sq(or other separators) on linux and windows or other > platform to Trafodion odb User Guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2065) Documentation of TO_CHAR, TO_DATE, TO_NUMBER
[ https://issues.apache.org/jira/browse/TRAFODION-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2065: Assignee: Liu Yu (was: liu ming) > Documentation of TO_CHAR, TO_DATE, TO_NUMBER > > > Key: TRAFODION-2065 > URL: https://issues.apache.org/jira/browse/TRAFODION-2065 > Project: Apache Trafodion > Issue Type: Bug > Components: documentation >Reporter: liu ming >Assignee: Liu Yu > > It is very hard to know how to use Trafodion TO_CHAR, the format is not fully > compatible with Oracle, and there are some limitations, without > documentation, it is hard to be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2102) Load data with # as fs in linux failed
[ https://issues.apache.org/jira/browse/TRAFODION-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2102: Assignee: zhangliang > Load data with # as fs in linux failed > -- > > Key: TRAFODION-2102 > URL: https://issues.apache.org/jira/browse/TRAFODION-2102 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-odb > Environment: centos6.7 > HBase 1.0.0-chd5.4.8 >Reporter: zhangliang >Assignee: zhangliang >Priority: Trivial > > load data with # as sp and " as fs failed > logs here: > Usecase : load with # as sp > Command : ./odb64luo -u trafodion -p traf123 -d traf -l > src=odb_auto_loadfile/load_data_3:pre=@scripts/ddl_person3.sql:tgt=trafodion.odb_test.person3:max=1000:rows=5000:parallel=5:loadcmd=UL:fs=#:sq=\" > Result : failed > During : 22s > Details : > odb [2016-07-07 16:47:04]: starting ODBC connection(s)... 0 1 2 3 4 5 > [0.0.0]Executing: 'drop table TRAFODION.odb_test.person3;' > [0.0.0]--- command executed in 16.499s (prep 0.002s, exec 16.497s, fetch > 0.000s/0.000s) > [0.0.1]Executing: 'CREATE TABLE TRAFODION.odb_test."PERSON3" (PID BIGINT > SIGNED NOT NULL,FNAME CHAR(20) NOT NULL,LNAME CHAR(20) NOT NULL,COUNTRY > VARCHAR(40) NOT NULL,CITY VARCHAR(40) NOT NULL,BDATE DATE NOT NULL,SEX > CHAR(1) NOT NULL,EMAIL VARCHAR(40) NOT NULL,SALARY NUMERIC(9,2) NOT NULL,EMPL > VARCHAR(40) NOT NULL,NOTES VARCHAR(80),LOADTS TIMESTAMP(0),PRIMARY KEY > (PID));' > [0.0.1]--- command executed in 1.460s (prep 0.002s, exec 1.458s, fetch > 0.000s/0.000s) > Connected to Trafodion > odb [Oload(7472)] - Error: row 1 col 1 field truncation. Input string: > >1#Jian-Guo#Pu#Canada#Xian#1927-10-07#U#ora...@qq.edu#190048#Google##2016-07-07 > 16:37:06< of length 91. This row won't be loaded > odb [Oload(7466)] - Warning: row 1 col 2 field truncation. Input string: > >2#Liang#Wu#US#Xian#1979-01-24#F#ap...@esgyn.cn#593561#Tencent##2016-07-07 > 16:37:06< of length 86. Only the first 20 char(s) will be loaded > odb [Oload(7466)] - Warning: row 1 col 3 field truncation. Input string: > >3#Yun-Peng#Luo#Canada#Guiyang#1943-09-18#M#ora...@163.org#119880#Microsoft#bb#2016-07-07 > 16:37:06< of length 101. Only the first 20 char(s) will be loaded > odb [Oload(7466)] - Warning: row 1 col 4 field truncation. Input string: > >4#Li-Ru#Yu#India#Xian#1982-01-05#F#le...@sina.com#693695#Esgyn#cc#2016-07-07 > 16:37:06< of length 89. Only the first 40 char(s) will be loaded > odb [Oload(7466)] - Warning: row 1 col 5 field truncation. Input string: > >5#Yun-Peng#Zhou#US#Guiyang#1977-02-03#M#ap...@163.org#586833#Google#cc#2016-07-07 > 16:37:06< of length 94. Only the first 40 char(s) will be loaded > odb [Oload(7472)] - Error: row 1 col 6 field truncation. Input string: > >6#Liang#Luo#Canada#Shanghai#1968-05-13#U#p...@esgyn.cn#980259#Apple#cc#2016-07-07 > 16:37:06< of length 94. This row won't be loaded > odb [Oload(7466)] - Warning: row 1 col 7 field truncation. Input string: > >7#Fu-Jin#Zhang#Canada#Shanghai#1964-08-02#M#p...@qq.edu#189402#Esgyn##2016-07-07 > 16:37:06< of length 93. Only the first 1 char(s) will be loaded > odb [Oload(7466)] - Warning: row 1 col 8 field truncation. Input string: > >8#Liang#Zhang#Canada#Guangzhou#1987-01-12#F#p...@sina.cn#1670621#Microsoft##2016-07-07 > 16:37:06< of length 99. Only the first 40 char(s) will be loaded > odb [Oload(7472)] - Error: row 1 col 9 field truncation. Input string: > >9#Shi-Fu#Yu#US#Beijing#2005-04-05#M#ap...@esgyn.cn#1045566#Microsoft##2016-07-07 > 16:37:06< of length 93. This row won't be loaded > odb [Oload(7466)] - Warning: row 1 col 10 field truncation. Input string: > >10#Liang#Wu#Canada#Shanghai#1917-07-18#M#ap...@163.cn#1810598#Esgyn#bb#2016-07-07 > 16:37:06< of length 94. Only the first 40 char(s) will be loaded > odb [Oload(7466)] - Warning: row 1 col 11 field truncation. Input string: > >11#Shi-Fu#Wu#Canada#Guangzhou#1966-05-30#M#ora...@gmail.org#1376463#Google#cc#2016-07-07 > 16:37:06< of length 101. Only the first 80 char(s) will be loaded > odb [Oload(7472)] - Error: row 1 col 12 field truncation. Input string: > >12#Liang#Wu#China#Shanghai#1999-09-05#M#ora...@gmail.org#306457#HP#bb#2016-07-07 > 16:37:06< of length 93. This row won't be loaded > ... > [0] odb version 1.1.0 Load statistics: > [0] Target table: TRAFODION.ODB_TEST.PERSON3 > [0] Source: odb_auto_loadfile/load_data_3 > [0] Pre-loading time: 21.917 s (00:00:21.917) > [0] Loading time: 0.052 s(00:00:00.052) > [0] Total records read: 833 > [0] Total records inserted: 0 > [0] Total number of columns: 12 > [0] Total bytes read: 1,138,306 > [0] Average input row size: 1,366.5 B > [0] ODBC row size: 341 B (data) + 96 B (len ind) > [0] Rowset size: 1,000 > [0] Rowset buffer size:
[jira] [Created] (TRAFODION-2117) add support of SQL extension 'EXCEPT'
liu ming created TRAFODION-2117: --- Summary: add support of SQL extension 'EXCEPT' Key: TRAFODION-2117 URL: https://issues.apache.org/jira/browse/TRAFODION-2117 Project: Apache Trafodion Issue Type: New Feature Reporter: liu ming add syntax and basic functional support for 'EXCEPT', meet the requirement to run TPCDS as initial goal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2117) add support of SQL extension 'EXCEPT'
[ https://issues.apache.org/jira/browse/TRAFODION-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2117: --- Assignee: liu ming > add support of SQL extension 'EXCEPT' > -- > > Key: TRAFODION-2117 > URL: https://issues.apache.org/jira/browse/TRAFODION-2117 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > > add syntax and basic functional support for 'EXCEPT', meet the requirement to > run TPCDS as initial goal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2103) Load data with " as sp and " as fs in linux failed
[ https://issues.apache.org/jira/browse/TRAFODION-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2103: Assignee: zhangliang > Load data with " as sp and " as fs in linux failed > -- > > Key: TRAFODION-2103 > URL: https://issues.apache.org/jira/browse/TRAFODION-2103 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-odb > Environment: centos6.7 > HBase 1.0.0 - cdh 5.4.8 >Reporter: zhangliang >Assignee: zhangliang >Priority: Trivial > > load data with " as sp and " as fs failed. > It is because the sp of first colume and the fs of second one matched, and > odb consider it is colume 2 and is a null string, meawhile, the table define > that colume 2 cannot be null. > logs here: > Usecase : load with " as sp > Command : ./odb64luo -u trafodion -p traf123 -d traf -l > src=odb_auto_loadfile/load_data_11:pre=@scripts/ddl_person3.sql:tgt=trafodion.odb_test.person3:max=1000:rows=5000:parallel=5:loadcmd=UL:fs=\":sq=\" > Result : failed > During : 36s > Details : > odb [2016-07-07 16:50:16]: starting ODBC connection(s)... 0 1 2 3 4 5 > [0.0.0]Executing: 'drop table TRAFODION.odb_test.person3;' > [0.0.0]--- command executed in 16.653s (prep 0.002s, exec 16.651s, fetch > 0.000s/0.000s) > [0.0.1]Executing: 'CREATE TABLE TRAFODION.odb_test."PERSON3" (PID BIGINT > SIGNED NOT NULL,FNAME CHAR(20) NOT NULL,LNAME CHAR(20) NOT NULL,COUNTRY > VARCHAR(40) NOT NULL,CITY VARCHAR(40) NOT NULL,BDATE DATE NOT NULL,SEX > CHAR(1) NOT NULL,EMAIL VARCHAR(40) NOT NULL,SALARY NUMERIC(9,2) NOT NULL,EMPL > VARCHAR(40) NOT NULL,NOTES VARCHAR(80),LOADTS TIMESTAMP(0),PRIMARY KEY > (PID));' > [0.0.1]--- command executed in 1.435s (prep 0.002s, exec 1.433s, fetch > 0.000s/0.000s) > Connected to Trafodion > [1] odb [Oloadbuff(9438)] - Error loading row 1 (State: 23000, Native 0) > [Trafodion ODBC Driver] GENERAL ERROR. Null Value in a non nullable column. > Row: 1 Column: 2 > >>> 1""Liang"""Yu"""Japan"""Beijing > [1] odb [Oloadbuff(9438)] - Error loading row 1 (State: 23000, Native 0) > [Trafodion ODBC Driver] GENERAL ERROR. Null Value in a non nullable column. > Row: 1 Column: 4 > >>> 1""Liang"""Yu"""Japan"""Beijing > [1] odb [Oloadbuff(9438)] - Error loading row 1 (State: 23000, Native 0) > [Trafodion ODBC Driver] GENERAL ERROR. Null Value in a non nullable column. > Row: 1 Column: 5 > >>> 1""Liang"""Yu"""Japan"""Beijing > [1] odb [Oloadbuff(9438)] - Error loading row 1 (State: 23000, Native 0) > [Trafodion ODBC Driver] GENERAL ERROR. Null Value in a non nullable column. > Row: 1 Column: 7 > >>> 1""Liang"""Yu"""Japan"""Beijing > ... > [1] 0 records inserted [commit] > [0] odb version 1.1.0 Load statistics: > [0] Target table: TRAFODION.ODB_TEST.PERSON3 > [0] Source: odb_auto_loadfile/load_data_11 > [0] Pre-loading time: 21.300 s (00:00:21.300) > [0] Loading time: 15.028 s(00:00:15.028) > [0] Total records read: 1,000 > [0] Total records inserted: 0 > [0] Total number of columns: 12 > [0] Total bytes read: 262,144 > [0] Average input row size: 262.1 B > [0] ODBC row size: 341 B (data) + 96 B (len ind) > [0] Rowset size: 1,000 > [0] Rowset buffer size: 426.76 KiB > [0] Load throughput (real data): 17.035 KiB/s > [0] Load throughput (ODBC): 0.000 KiB/s > [0] Reader Total/Wait Cycles: 1/0 > odb [2016-07-07 16:50:52]: exiting. Session Elapsed time 36.339 seconds > (00:00:36.339) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] liu ming updated TRAFODION-2104: Assignee: zhangliang > 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] [Commented] (TRAFODION-1538) Trafodion external tables not dropped when native HBase table is dropped.
[ https://issues.apache.org/jira/browse/TRAFODION-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379362#comment-15379362 ] liu ming commented on TRAFODION-1538: - Hi, Roberta, Could you explain more about this issue? How to reproduce it? thanks, Ming > Trafodion external tables not dropped when native HBase table is dropped. > - > > Key: TRAFODION-1538 > URL: https://issues.apache.org/jira/browse/TRAFODION-1538 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmu >Reporter: Roberta Marton >Assignee: liu ming > > In order to perform SQL operations on native tables, special Trafodion > external tables are created to match the associated native tables. When an > HBase native table is dropped, the corresponding Trafodion external table > should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1605) sqstart hangs if ulimits not correct
[ https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1605 started by liu ming. --- > sqstart hangs if ulimits not correct > > > Key: TRAFODION-1605 > URL: https://issues.apache.org/jira/browse/TRAFODION-1605 > Project: Apache Trafodion > Issue Type: Bug > Components: Build Infrastructure >Reporter: Roberta Marton >Assignee: liu ming > > If someone downloads a source tar file or uses the Trafodion git repository, > after building they need to install the results on their system. If the > ulimits on the system are not sufficient, then sqlci start hangs. The > customer has to kill sqlci and then kill all the processes in flight. > This happens when you perform the build instructions and choose the > "install_local_hadoop" option. The Trafodion Installer should already be > checking for this situation. > Perhaps add a check before sqlci starts to make sure the correct limits are > set. > Recommended limits: > ulimit –a > core file size(blocks, -c) 100 > data seg size(kbytes, -d) unlimited > scheduling priority(-e) 0 > file size (blocks, -f) unlimited > pending signals(-i) 515196 > max locked memory (kbytes, -l) 49595556 > max memory size (kbytes, -m) unlimited > open files (-n) 32000 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 10240 > cpu time (seconds, -t) unlimited > max user processes (-u) 267263 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1999) trafodion init failed, have to remove /trafodion znode to continue
[ https://issues.apache.org/jira/browse/TRAFODION-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380771#comment-15380771 ] liu ming commented on TRAFODION-1999: - not reproducible > trafodion init failed, have to remove /trafodion znode to continue > -- > > Key: TRAFODION-1999 > URL: https://issues.apache.org/jira/browse/TRAFODION-1999 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > Error during initialize trafodion. > Error msg in log file shows: > 2016-05-18 08:44:18,876, INFO, MON, Node Number: 0,, PIN: 23596 , Process > Name: $MONITOR,,, TID: 23599, Message ID: 101130801, STDERR redirected from > test01.$TM0.0.23982: > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:661) > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126) > ... 6 more > Exception in thread "main" java.lang.RuntimeException: > org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:244) > Caused by: org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:226) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:240) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:140) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:3601) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:539) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:471) > at > org.apache.hadoop.hbase.client.transactional.TmDDL.(TmDDL.java:93) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:239) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.TableExistsException): > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL
[jira] [Resolved] (TRAFODION-1524) UPSERT failure with generator error
[ https://issues.apache.org/jira/browse/TRAFODION-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1524. - Resolution: Cannot Reproduce Fix Version/s: 2.1-incubating probably fixed by other changes > UPSERT failure with generator error > --- > > Key: TRAFODION-1524 > URL: https://issues.apache.org/jira/browse/TRAFODION-1524 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 1.2-incubating > Environment: Workstation development environment >Reporter: David Wayne Birdsall >Assignee: liu ming > Fix For: 2.1-incubating > > > The following log shows an UPSERT statement that fails in the generator. The > target table has an index on a non-key column, and the UPSERT statement has a > BETWEEN predicate on that same column. Take away either of these conditions > and the failure goes away. > >>obey TestBadUpsert(setup1); > >>drop table if exists T1; > --- SQL operation complete. > >>drop table if exists T1backup; > --- SQL operation complete. > >> > >>create table T1 > +> ( a integer not null, > +> b integer not null, > +> c integer not null, > +> d char(80), > +> primary key (a) ) > +>salt using 4 partitions; > --- SQL operation complete. > >> > >> > >>insert into T1 values (1,1,1,'hi there!'), > +> (2,1,1,'a somewhat longer string'), > +> (3,2,2,'Now is the time for all good men to come to the aid of their > country > .'), > +> (4,3,3,' '); > --- 4 row(s) inserted. > >> > >> > >>-- create another table just like T1 > >>create table T1backup like T1; > --- SQL operation complete. > >> > >>insert into T1backup select * from T1; > --- 4 row(s) inserted. > >> > >>obey TestBadUpsert(setup2); > >> > >>create index iT1b on T1(b); > --- SQL operation complete. > >> > >>obey TestBadUpsert(badupsert); > >> > >>-- this upsert fails. Taking out the "between" (say, replacing > >>-- it with an equality predicate) eliminates the failure. > >>-- Taking out the index on b also eliminates the failure. > >>upsert into T1 select * from T1backup where b between 1 and 2; > *** ERROR[7000] An internal error occurred in the code generator in file > ../gene > rator/GenPreCode.cpp at line 1313: valuesToBeBound.isEmpty(). > *** ERROR[2235] Compiler Internal Error: An unknown error, originated from > file > ../generator/Generator.cpp at line 2810. > *** ERROR[8822] The statement was not prepared. > >> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1524) UPSERT failure with generator error
[ https://issues.apache.org/jira/browse/TRAFODION-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380784#comment-15380784 ] liu ming commented on TRAFODION-1524: - fixed by some other changes, not reproducible now. > UPSERT failure with generator error > --- > > Key: TRAFODION-1524 > URL: https://issues.apache.org/jira/browse/TRAFODION-1524 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 1.2-incubating > Environment: Workstation development environment >Reporter: David Wayne Birdsall >Assignee: liu ming > > The following log shows an UPSERT statement that fails in the generator. The > target table has an index on a non-key column, and the UPSERT statement has a > BETWEEN predicate on that same column. Take away either of these conditions > and the failure goes away. > >>obey TestBadUpsert(setup1); > >>drop table if exists T1; > --- SQL operation complete. > >>drop table if exists T1backup; > --- SQL operation complete. > >> > >>create table T1 > +> ( a integer not null, > +> b integer not null, > +> c integer not null, > +> d char(80), > +> primary key (a) ) > +>salt using 4 partitions; > --- SQL operation complete. > >> > >> > >>insert into T1 values (1,1,1,'hi there!'), > +> (2,1,1,'a somewhat longer string'), > +> (3,2,2,'Now is the time for all good men to come to the aid of their > country > .'), > +> (4,3,3,' '); > --- 4 row(s) inserted. > >> > >> > >>-- create another table just like T1 > >>create table T1backup like T1; > --- SQL operation complete. > >> > >>insert into T1backup select * from T1; > --- 4 row(s) inserted. > >> > >>obey TestBadUpsert(setup2); > >> > >>create index iT1b on T1(b); > --- SQL operation complete. > >> > >>obey TestBadUpsert(badupsert); > >> > >>-- this upsert fails. Taking out the "between" (say, replacing > >>-- it with an equality predicate) eliminates the failure. > >>-- Taking out the index on b also eliminates the failure. > >>upsert into T1 select * from T1backup where b between 1 and 2; > *** ERROR[7000] An internal error occurred in the code generator in file > ../gene > rator/GenPreCode.cpp at line 1313: valuesToBeBound.isEmpty(). > *** ERROR[2235] Compiler Internal Error: An unknown error, originated from > file > ../generator/Generator.cpp at line 2810. > *** ERROR[8822] The statement was not prepared. > >> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1676) support better runtime error message when a SQL function meet fital error
[ https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1676. - Resolution: Fixed Fix Version/s: 2.1-incubating temp fixed, if meet more SQL error need enhance msg, reopen this. > support better runtime error message when a SQL function meet fital error > - > > Key: TRAFODION-1676 > URL: https://issues.apache.org/jira/browse/TRAFODION-1676 > Project: Apache Trafodion > Issue Type: Improvement > Components: sql-exe >Reporter: liu ming >Assignee: liu ming >Priority: Minor > Fix For: 2.1-incubating > > > A sql contains some SQL function, for example UPPER(), when the input data of > UPPER() contains invalid data, UPPER() will fail. In this case, the whole > query abort, and the error message cannot tell which row has invalid data, so > it is very hard to fix the problem. > It will be good to have row id or the real value of the error row in the > error message to help trouble shooting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1999) trafodion init failed, have to remove /trafodion znode to continue
[ https://issues.apache.org/jira/browse/TRAFODION-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1999. - Resolution: Cannot Reproduce > trafodion init failed, have to remove /trafodion znode to continue > -- > > Key: TRAFODION-1999 > URL: https://issues.apache.org/jira/browse/TRAFODION-1999 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > Error during initialize trafodion. > Error msg in log file shows: > 2016-05-18 08:44:18,876, INFO, MON, Node Number: 0,, PIN: 23596 , Process > Name: $MONITOR,,, TID: 23599, Message ID: 101130801, STDERR redirected from > test01.$TM0.0.23982: > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:661) > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126) > ... 6 more > Exception in thread "main" java.lang.RuntimeException: > org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:244) > Caused by: org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:226) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:240) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:140) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:3601) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:539) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:471) > at > org.apache.hadoop.hbase.client.transactional.TmDDL.(TmDDL.java:93) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:239) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.TableExistsException): > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at >
[jira] [Resolved] (TRAFODION-1731) Compiler asserts in preCodeGen phase when compile a UPSERT stmt
[ https://issues.apache.org/jira/browse/TRAFODION-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1731. - Resolution: Duplicate Fix Version/s: 2.1-incubating Duplicated with JIRA 2021 > Compiler asserts in preCodeGen phase when compile a UPSERT stmt > --- > > Key: TRAFODION-1731 > URL: https://issues.apache.org/jira/browse/TRAFODION-1731 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Reporter: Qifan Chen >Assignee: liu ming > Fix For: 2.1-incubating > > > Compiler asserts in preCodeGen phase with the following message. > *** ERROR[7000] An internal error occurred in the code generator in file > ../generator/GenPreCode.cpp at line 1313: > valuesToBeBound.isEmpty(). > The query involved is as follows. > >>prepare xx from > +>UPSERT INTO PartDPartE (ID, dataPartEPartCID, valuePartDID) VALUES > +>(NVL( > +>(select a.id from PartDPartE a where a.dataPartEPartCID = (select b.id from > PartDPartEPartC b where b > .codeValue = '/literal1[itemID]') and a.valuePartDID = (select c.id from > ValuePartD c where c.dataType = > 'array' and c.partF is null and c.xxlength is null and c.zzlength is null and > c.xxItems is null and c.zzItems > is null ) ), DEFAULT), > +>(select d.id from PartDPartEPartC d where d.codeValue = > '/literal1[itemID]'), > +>(select e.id from ValuePartD e where e.dataType = 'array' and e.partF is > null and e.xxlength is null and e.m > axlength is null and e.xxItems is null and e.zzItems is null ) > +>) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2035) Not able to copy table where there is column with type timestamp(0), error out with ERROR[8102]
[ https://issues.apache.org/jira/browse/TRAFODION-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2035: Assignee: zhangliang (was: liu ming) > Not able to copy table where there is column with type timestamp(0), error > out with ERROR[8102] > --- > > Key: TRAFODION-2035 > URL: https://issues.apache.org/jira/browse/TRAFODION-2035 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-odb > Environment: centos6.7 HBase 1.0.0-cdh5.4.8 >Reporter: zhangliang >Assignee: zhangliang > > This issue is from mantis 72. > -> Create table as following in both oracle and trafodion: > CREATE TABLE t_timestamp_0 ( > PID int NOT NULL > ,LOADTS TIMESTAMP(0) > ,PRIMARY KEY (PID) > ); > -> insert data into oracle table > begin > for i in 1 .. 1000 > loop > insert into t_timestamp_0 values (i,systimestamp); > end loop; > commit; > end; > / > -> using odb command as below to copy data to trafodion table, it is expected > to success, but failed with 8102 error > @dev1 odb_test]$ odb64luo -u jason:trafodion -p jason:traf123 -d > OracleODBC-11g:traf -cp > src=T_TIMESTAMP_0:tgt=trafodion.ODB_TEST.T_TIMESTAMP_0:rows=m2:truncate:parallel=2:splitby=pid > -T 6 -v > Connected to Oracle > odb [2015-10-24 00:19:45]: starting ODBC connection(s)... 0 >1 >2 3 >4 >5 > Connected to Trafodion > odb: Now truncating target table (DELETE FROM > trafodion.ODB_TEST.T_TIMESTAMP_0) > [4.0.0]--- 0 row(s) deleted in 19.491s (prep 19.442s, exec 0.049s, fetch > 0.000s/0.000s) > [3] odb [Ocopy(10206)] - SOURCE statement: SELECT * FROM T_TIMESTAMP_0 WHERE > pid >= 500 AND pid < 1001 > [0] odb [Ocopy(10206)] - SOURCE statement: SELECT * FROM T_TIMESTAMP_0 WHERE > pid >= 1 AND pid < 500 > [0] odb [Ocopy(10548)] - TARGET statement: INSERT INTO > trafodion.ODB_TEST.T_TIMESTAMP_0 VALUES (?,?) > [3] odb [Ocopy(10548)] - TARGET statement: INSERT INTO > trafodion.ODB_TEST.T_TIMESTAMP_0 VALUES (?,?) > [1] odb [Oloadbuff(9437)] - Error loading row 3 (State: 23000, Native -8102) > [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** ERROR[8102] The > operation is prevented by a unique constraint. [2015-10-24 00:20:21] Row: 3 > [1] 0 records copied [commit] > [4] odb [Oloadbuff(9437)] - Error loading row 3 (State: 23000, Native -8102) > [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** ERROR[8102] The > operation is prevented by a unique constraint. [2015-10-24 00:20:22] Row: 3 > [4] odb [Oloadbuff(9464)] - Unable to get row counts from driver > [4] odb(9465) [2015-10-24 00:20:23] - [unixODBC][Driver Manager]Function > sequence error (State: HY010 Native Err: 0) > [4] odb(9465) [2015-10-24 00:20:23] - [Trafodion ODBC Driver][Trafodion > Database] SQL ERROR:*** ERROR[8102] The operation is prevented by a unique > constraint. [2015-10-24 00:20:22] Row: 3 (State: 23000 Native Err: -8102) > [4] 0 records copied [commit] > odb: thread 2 closing connection... > odb: thread 2 is ending... > odb: thread 1 closing connection... > odb: thread 5 closing connection... > odb: thread 5 is ending... > odb: thread 0 closing connection... > odb: thread 0 is ending... > odb: thread 1 is ending... > odb: thread 4 closing connection... > [3] odb version 1.1.0 Copy statistics: > [0] Source: T_TIMESTAMP_0 > [0] Target: trafodion.ODB_TEST.T_TIMESTAMP_0 > [0] Total number of columns: 2 > [0] ODBC row size: 62 B (data) + 16 B (len ind) > [0] Rowset size: 26,886 > [0] Rowset buffer size: 2,047.96 KiB > [0] Pre-copy time: 28.434 s (00:00:28.434) > [0] Copy time: 8.812 s (00:00:08.812) > [0] Total records copied: 0 (0.000 krec/s) > [0] Copy throughput (ODBC): 0.000 MiB/s (0.000 GiB/h) > [0] Total/Wait cycles: 1/0 > [0>1] 0 records copied in 9.297 (00:00:09.297 s) > [0>2] 0 records copied in 9.257 (00:00:09.257 s) > [3] Total/Wait cycles: 1/0 > [3>4] 0 records copied in 8.811 (00:00:08.811 s) > [3>5] 0 records copied in 8.769 (00:00:08.769 s) > odb: thread 4 is ending... > odb: thread 3 closing connection... > odb: thread 3 is ending... > odb [2015-10-24 00:20:23]: exiting. Session Elapsed time 37.287 seconds > (00:00:37.287) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1108) LP Bug: 1438467 - dtmci should return "status trans" output in JSON format
[ https://issues.apache.org/jira/browse/TRAFODION-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming closed TRAFODION-1108. --- Resolution: Won't Fix no HPDSM anymore > LP Bug: 1438467 - dtmci should return "status trans" output in JSON format > -- > > Key: TRAFODION-1108 > URL: https://issues.apache.org/jira/browse/TRAFODION-1108 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm >Reporter: Joanie Cooper >Assignee: liu ming >Priority: Critical > Fix For: 2.1-incubating > > > To support the HPDSM team, the "dtmci" tooling should return the "status > trans" command output in JSON format. > This will be needed for the Trafodion R1.2 release. > Assigned to LaunchPad User Adriana Fuentes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1264) LP Bug: 1463126 - Support SSCC coprocessor in HBase on clusters
[ https://issues.apache.org/jira/browse/TRAFODION-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming closed TRAFODION-1264. --- Resolution: Won't Fix SSCC will be redesgined and redo > LP Bug: 1463126 - Support SSCC coprocessor in HBase on clusters > --- > > Key: TRAFODION-1264 > URL: https://issues.apache.org/jira/browse/TRAFODION-1264 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Joanie Cooper >Assignee: liu ming > > Please add the SsccRegionEndpoint coprocessor to the HBase regionserver > coprocessor list for Trafodion coprocessors on a cluster. This is already > configured for the workstation in "install_local_hadoop". > HBase on the cluster will need four Trafodion C++ libraries to support the > global id mechanism needed for SSCC configurations; libidtm.so, libsbms.so, > libsbutil.so and libsblogalt.so. > These libraries can be found in the Trafodion instance > "$MY_SQROOT/export/lib64" directory. > The default for Trafodion will remain at MVCC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1966) [offline backup] TrafexportSnapshot ran into NoClassDefFoundError on HDP2.4
[ https://issues.apache.org/jira/browse/TRAFODION-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382045#comment-15382045 ] liu ming commented on TRAFODION-1966: - Is this still an issue? > [offline backup] TrafexportSnapshot ran into NoClassDefFoundError on > HDP2.4 > > > Key: TRAFODION-1966 > URL: https://issues.apache.org/jira/browse/TRAFODION-1966 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-backup-restore > Environment: centos6.7, hbase1.1 HDP2.4.0 >Reporter: Gao, Rui-Xian >Assignee: liu ming > > offline backup on HDP2.4.0 will run into error -- > ./run_full_trafodion_backup.sh > Exporting TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 ... > hbase org.trafodion.utility.backuprestore.TrafExportSnapshot -snapshot > TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 -copy-to > hdfs://suse-0.novalocal:8020/trafodion_backups/backup_20160503-2207/TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 > -mappers 0 -mr-lowlimit-mb 100 > 2016-05-03 22:09:49,141 INFO [main] backuprestore.TrafExportSnapshot: > Trafodion Export Snapshot Utility > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/2.3.4.7-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/2.3.4.7-4/zookeeper/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] > 2016-05-03 22:09:50,797 INFO [main] backuprestore.TrafExportSnapshot: Copy > Snapshot Manifest > 2016-05-03 22:09:51,246 INFO [main] backuprestore.TrafExportSnapshot: > Loading Snapshot 'TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207' hfile list > 2016-05-03 22:09:51,487 INFO [main] backuprestore.TrafExportSnapshot: Copy > Snapshot Data Files > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/hadoop/hbase/mob/MobUtils > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.getCopyInputPath(TrafExportSnapshot.java:1052) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.run(TrafExportSnapshot.java:983) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.innerMain(TrafExportSnapshot.java:1109) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.main(TrafExportSnapshot.java:1114) > Caused by: java.lang.ClassNotFoundException: > org.apache.hadoop.hbase.mob.MobUtils > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > ***[ERROR]: Error while exporting snapshot: > TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207. > For more information please check the logs at > /home/trafodion/esgynDBadv-20160501_0830-bin/hbase_utilities/backup_and_restore/logs/run_traf_backup_20160503-2207.log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1564) Region split/balance is not being delayed if Trx Scanner obj is present
[ https://issues.apache.org/jira/browse/TRAFODION-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1564. - Resolution: Fixed Already fixed by Oliver > Region split/balance is not being delayed if Trx Scanner obj is present > --- > > Key: TRAFODION-1564 > URL: https://issues.apache.org/jira/browse/TRAFODION-1564 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm >Reporter: Oliver Bucaojit >Assignee: liu ming > > A region move/split/rebalance should be delayed when a TransactionalScanner > is present on the region coprocessor 'scanners' list. The delay is not > happening and is throwing the following error: > *** ERROR[8448] Unable to access Hbase interface. Call to > ExpHbaseInterface::nextRow returned error HBASE_ACCESS_ERROR(-706). Cause: > java.util.concurrent.ExecutionException: java.io.IOException: PerformScan > error on coprocessor call, scannerID: 0 java.io.IOException: performScan > encountered Exception txID: 562962838798562 Exception: > org.apache.hadoop.hbase.UnknownScannerException: ScannerId: 0, already closed? > While debugging I noticed that in the SplitBalanceHelper the code is waiting > for clear scanners list && pending txn list. It should be '||' instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1564) Region split/balance is not being delayed if Trx Scanner obj is present
[ https://issues.apache.org/jira/browse/TRAFODION-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming closed TRAFODION-1564. --- > Region split/balance is not being delayed if Trx Scanner obj is present > --- > > Key: TRAFODION-1564 > URL: https://issues.apache.org/jira/browse/TRAFODION-1564 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm >Reporter: Oliver Bucaojit >Assignee: liu ming > > A region move/split/rebalance should be delayed when a TransactionalScanner > is present on the region coprocessor 'scanners' list. The delay is not > happening and is throwing the following error: > *** ERROR[8448] Unable to access Hbase interface. Call to > ExpHbaseInterface::nextRow returned error HBASE_ACCESS_ERROR(-706). Cause: > java.util.concurrent.ExecutionException: java.io.IOException: PerformScan > error on coprocessor call, scannerID: 0 java.io.IOException: performScan > encountered Exception txID: 562962838798562 Exception: > org.apache.hadoop.hbase.UnknownScannerException: ScannerId: 0, already closed? > While debugging I noticed that in the SplitBalanceHelper the code is waiting > for clear scanners list && pending txn list. It should be '||' instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364404#comment-15364404 ] liu ming commented on TRAFODION-1673: - To fully support WITH, I agree with both Hans and QiFan. Especially the idea of evaluating the CTE only once. However, we can do this step by step. The very first step is as Hans' suggest, Trafodion support WITH function in the parser. The 'Temp View' can be simply be a 'subquery', which is a RenameTable in the parse tree. As initial testing, it can support recursive reference as well, but with limitation that the WITH definition must occur before it is referred , for example: with w1 as (select * from witht1), w2 as (select * from w1) select * from w2; is good, since w1 is defined before it is used in w2. But with w1 as (select * from w2), w2 as (select * from t1) select * from w1; will not work, however, I don't see the second usage in all TPCDS queries. So I feel it should be good enough to support the first syntax. This first iteration can implement the functionality, and parser change can be reused later of a 'common CTE', and test case can be used also. Later, we can implement a new CTE type of node, which can feed multiple data consumers, but I feel that is not easy in current architecture. > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2096) create all tpcds hive external tables from install_local_hadoop
[ https://issues.apache.org/jira/browse/TRAFODION-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2096 started by liu ming. --- > create all tpcds hive external tables from install_local_hadoop > --- > > Key: TRAFODION-2096 > URL: https://issues.apache.org/jira/browse/TRAFODION-2096 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: liu ming >Priority: Minor > > store_returns > catalog_sales > catalog_returns > web_sales > web_returns > inventory > call_center > catalog_page > web_site > Web_page > warehouse > income_band > reason > ship_mode > These tables were used by TPCDS queries, it will help to automatically > install them in a dev environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1676) support better runtime error message when a SQL function meet fital error
[ https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362591#comment-15362591 ] liu ming commented on TRAFODION-1676: - This PR (564) enhance error messages for these SQL Errors: EXE_CONVERTTIMESTAMP_ERROR = 8405, EXE_JULIANTIMESTAMP_ERROR = 8407, EXE_CONVERT_STRING_ERROR = 8413 EXE_CONVERT_DATETIME_ERROR = 8415, By displaying the offending source data content, for CONVERT_STRING_ERROR, because it always contains multi-byte character, so display the data in HEX mode. > support better runtime error message when a SQL function meet fital error > - > > Key: TRAFODION-1676 > URL: https://issues.apache.org/jira/browse/TRAFODION-1676 > Project: Apache Trafodion > Issue Type: Improvement > Components: sql-exe >Reporter: liu ming >Assignee: liu ming >Priority: Minor > > A sql contains some SQL function, for example UPPER(), when the input data of > UPPER() contains invalid data, UPPER() will fail. In this case, the whole > query abort, and the error message cannot tell which row has invalid data, so > it is very hard to fix the problem. > It will be good to have row id or the real value of the error row in the > error message to help trouble shooting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2117) add support of SQL extension 'EXCEPT'
[ https://issues.apache.org/jira/browse/TRAFODION-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2117. - Resolution: Fixed Fix Version/s: 2.1-incubating > add support of SQL extension 'EXCEPT' > -- > > Key: TRAFODION-2117 > URL: https://issues.apache.org/jira/browse/TRAFODION-2117 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > add syntax and basic functional support for 'EXCEPT', meet the requirement to > run TPCDS as initial goal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390677#comment-15390677 ] liu ming commented on TRAFODION-2121: - from Hive 0.13, Decimal is changed, it is too complex to find out hive version at compile time, so Trafodion treat 'decimal' in Hive as it is after Hive0.13. and hive definitions is from https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types#LanguageManualTypes-decimal > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2090) improve the very first time of query compiling
liu ming created TRAFODION-2090: --- Summary: improve the very first time of query compiling Key: TRAFODION-2090 URL: https://issues.apache.org/jira/browse/TRAFODION-2090 Project: Apache Trafodion Issue Type: Improvement Reporter: liu ming Currently, the very first query run in master executor: sqlci or mxosrvr will take seconds to compile. Initial analysis shows most time spend on metadata retrieving. Need to improve the compile time for the very first time, at least from end user's perspective. Speed up the metadata retrieval speed. Redesign metadata scheme Prefetch metadata are all among possible solutions, the aim is to shorten the time spend on the SQL compile for the first time. Initial goal is within 1 second, faster the better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2089) JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by traf_tools_setup.sh
[ https://issues.apache.org/jira/browse/TRAFODION-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2089. - Resolution: Fixed Fix Version/s: 2.1-incubating > JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by > traf_tools_setup.sh > -- > > Key: TRAFODION-2089 > URL: https://issues.apache.org/jira/browse/TRAFODION-2089 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > In Development enviorment, one can simply use traf_tools_setup.sh to install > thirdparty libraries, including log4cxx. > Most components Makefile will contain include path of that log4cxx, but > JDBC_T2 not, so if one doesn't install log4cxx in system path, build fail. > It is better to add log4cxx path into Makefile -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2085) Installer will not able to upgrade instance successfully if hbase_trx_jar file version changed
[ https://issues.apache.org/jira/browse/TRAFODION-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2085: Assignee: Amanda Moran (was: liu ming) > Installer will not able to upgrade instance successfully if hbase_trx_jar > file version changed > -- > > Key: TRAFODION-2085 > URL: https://issues.apache.org/jira/browse/TRAFODION-2085 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Affects Versions: 2.1-incubating >Reporter: Jianguo Zhou (Jason) >Assignee: Amanda Moran > > The installer will try to hbase_trx_jar file from /var/lib/trafodion to the > Hadoop distros location, and there was one hbase-trx-hdp2_3-2.0.0.jar out > there, then we run the upgrade, it will have anther > hbase-trx-hdp2_3-2.1.0.jar in the /var/lib/trafodion too, means 2 trx jar > file will be copied to Hadoop distros location, then the installer will fail > for checking logic as following: > for node in $HBASE_NODES > do >copiedOver=$(ssh -q -n $node sudo ls $HADOOP_PATH/hbase-trx* | wc -l) >if [[ $copiedOver -ne "1" ]]; then <-- 2 not equal 1, so failed then > echo "***ERROR: $hbase_trx_jar was not copied on $node" > echo "***ERROR: Please investigate why this happened" > echo "***ERROR: Trafodion can not start without this. EXITING..." > exit -1 >fi > done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2085) Installer will not able to upgrade instance successfully if hbase_trx_jar file version changed
[ https://issues.apache.org/jira/browse/TRAFODION-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2085: --- Assignee: liu ming > Installer will not able to upgrade instance successfully if hbase_trx_jar > file version changed > -- > > Key: TRAFODION-2085 > URL: https://issues.apache.org/jira/browse/TRAFODION-2085 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Affects Versions: 2.1-incubating >Reporter: Jianguo Zhou (Jason) >Assignee: liu ming > > The installer will try to hbase_trx_jar file from /var/lib/trafodion to the > Hadoop distros location, and there was one hbase-trx-hdp2_3-2.0.0.jar out > there, then we run the upgrade, it will have anther > hbase-trx-hdp2_3-2.1.0.jar in the /var/lib/trafodion too, means 2 trx jar > file will be copied to Hadoop distros location, then the installer will fail > for checking logic as following: > for node in $HBASE_NODES > do >copiedOver=$(ssh -q -n $node sudo ls $HADOOP_PATH/hbase-trx* | wc -l) >if [[ $copiedOver -ne "1" ]]; then <-- 2 not equal 1, so failed then > echo "***ERROR: $hbase_trx_jar was not copied on $node" > echo "***ERROR: Please investigate why this happened" > echo "***ERROR: Trafodion can not start without this. EXITING..." > exit -1 >fi > done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2088) support null last and null first in ORDER BY
liu ming created TRAFODION-2088: --- Summary: support null last and null first in ORDER BY Key: TRAFODION-2088 URL: https://issues.apache.org/jira/browse/TRAFODION-2088 Project: Apache Trafodion Issue Type: Improvement Reporter: liu ming Priority: Minor handle the syntax ‘order by nulls last’ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2089) JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by traf_tools_setup.sh
liu ming created TRAFODION-2089: --- Summary: JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by traf_tools_setup.sh Key: TRAFODION-2089 URL: https://issues.apache.org/jira/browse/TRAFODION-2089 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming In Development enviorment, one can simply use traf_tools_setup.sh to install thirdparty libraries, including log4cxx. Most components Makefile will contain include path of that log4cxx, but JDBC_T2 not, so if one doesn't install log4cxx in system path, build fail. It is better to add log4cxx path into Makefile -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2089) JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by traf_tools_setup.sh
[ https://issues.apache.org/jira/browse/TRAFODION-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2089: --- Assignee: liu ming > JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by > traf_tools_setup.sh > -- > > Key: TRAFODION-2089 > URL: https://issues.apache.org/jira/browse/TRAFODION-2089 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > In Development enviorment, one can simply use traf_tools_setup.sh to install > thirdparty libraries, including log4cxx. > Most components Makefile will contain include path of that log4cxx, but > JDBC_T2 not, so if one doesn't install log4cxx in system path, build fail. > It is better to add log4cxx path into Makefile -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2089) JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by traf_tools_setup.sh
[ https://issues.apache.org/jira/browse/TRAFODION-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2089 started by liu ming. --- > JDBC_T2 Makefile not add INCLUDE path for log4cxx installed by > traf_tools_setup.sh > -- > > Key: TRAFODION-2089 > URL: https://issues.apache.org/jira/browse/TRAFODION-2089 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > In Development enviorment, one can simply use traf_tools_setup.sh to install > thirdparty libraries, including log4cxx. > Most components Makefile will contain include path of that log4cxx, but > JDBC_T2 not, so if one doesn't install log4cxx in system path, build fail. > It is better to add log4cxx path into Makefile -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-1999) trafodion init failed, have to remove /trafodion znode to continue
[ https://issues.apache.org/jira/browse/TRAFODION-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-1999: --- Assignee: liu ming > trafodion init failed, have to remove /trafodion znode to continue > -- > > Key: TRAFODION-1999 > URL: https://issues.apache.org/jira/browse/TRAFODION-1999 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > Error during initialize trafodion. > Error msg in log file shows: > 2016-05-18 08:44:18,876, INFO, MON, Node Number: 0,, PIN: 23596 , Process > Name: $MONITOR,,, TID: 23599, Message ID: 101130801, STDERR redirected from > test01.$TM0.0.23982: > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:661) > at org.apache.hadoop.hbase.client.HBaseAdmin$5.call(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126) > ... 6 more > Exception in thread "main" java.lang.RuntimeException: > org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:244) > Caused by: org.apache.hadoop.hbase.TableExistsException: > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:161) > at > org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:129) > at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1279) > at > org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:399) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:42436) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2033) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107) > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) > at java.lang.Thread.run(Thread.java:745) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:226) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:240) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:140) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:3601) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:657) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:539) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:471) > at > org.apache.hadoop.hbase.client.transactional.TmDDL.(TmDDL.java:93) > at org.trafodion.dtm.HBaseTxClient.init(HBaseTxClient.java:239) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.TableExistsException): > org.apache.hadoop.hbase.TableExistsException: TRAFODION._DTM_.TDDL > at >
[jira] [Issue Comment Deleted] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1673: Comment: was deleted (was: It can be first implemented using sub-query, that is, to replace each WITH clause by a sub query. (RenamedTable) CTE mentioned by QiFan is a great idea, and we can set it as a final goal. To meet the functional requirement, we can simply use subquery in the first iteration.) > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1976) SQL reference manual should add description of the 'create unique index' syntax
[ https://issues.apache.org/jira/browse/TRAFODION-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-1976: Assignee: Suresh Subbiah (was: liu ming) > SQL reference manual should add description of the 'create unique index' > syntax > --- > > Key: TRAFODION-1976 > URL: https://issues.apache.org/jira/browse/TRAFODION-1976 > Project: Apache Trafodion > Issue Type: Bug > Components: documentation >Reporter: liu ming >Assignee: Suresh Subbiah > > Trafodion support creation of unique index, which will add a unique > constraint and will use fewer key columns (Saving space and more efficient). > However, the SQL Reference Manual does not mention this syntax in CREATE > INDEX section, should add it. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1911) A special mode to be more tolerant during bulkloading and accessing HDFS raw data
[ https://issues.apache.org/jira/browse/TRAFODION-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1911. - Resolution: Fixed Fix Version/s: 2.0-incubating > A special mode to be more tolerant during bulkloading and accessing HDFS raw > data > - > > Key: TRAFODION-1911 > URL: https://issues.apache.org/jira/browse/TRAFODION-1911 > Project: Apache Trafodion > Issue Type: Umbrella >Reporter: liu ming >Assignee: liu ming > Fix For: 2.0-incubating > > > Raw data in HDFS sometimes are not well formatted or contains bad values. > Trafodion bulkloader will complain error or not work well by default once > that is the case. > It will be valuable to let Trafodion work in a special mode to tolerate bad > raw data in the HDFS. A not completed list below: > 1.Automatically remove ‘\r’ when it is used as ‘\r\n’ the DOS format line > delimiter. > 2.Donot raise SQL error, but convert bad data into null automatically, > and still be able to log this into error log files when required, don’t make > this change silent, and make this action traceable. > 3.Allow ‘\n’ in data field even ‘\n’ is the line terminator > 4.Auto truncate overflowed string, log it into the error log file, in > order to make it traceable. > 5.Tolerate ‘\0’ in source data > There may be more, this is an umbrella JIRA to track all related sub tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1673 started by liu ming. --- > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359961#comment-15359961 ] liu ming commented on TRAFODION-1673: - It can be first implemented using sub-query, that is, to replace each WITH clause by a sub query. (RenamedTable) CTE mentioned by QiFan is a great idea, and we can set it as a final goal. To meet the functional requirement, we can simply use subquery in the first iteration. > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1566) Ungraceful failure when transaction size limit reached
[ https://issues.apache.org/jira/browse/TRAFODION-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1566. - Resolution: Duplicate Fix Version/s: 2.1-incubating dup with TRAFODION-2046 > Ungraceful failure when transaction size limit reached > -- > > Key: TRAFODION-1566 > URL: https://issues.apache.org/jira/browse/TRAFODION-1566 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm, sql-exe >Affects Versions: 1.3-incubating >Reporter: David Wayne Birdsall >Assignee: liu ming >Priority: Minor > Fix For: 2.1-incubating > > > When exceeding transaction size limits, DELETE fails with a puzzling error > message. > The following script produces the problem on a workstation (using > install_local_hadoop, so the HMaster process is handling all four regions). > Best results if the setup section is done in a separate sqlci from the > deleteTest section (so you get current statistics): > ?section setup > create schema DeleteFailure; > set schema DeleteFailure; > -- create a table saltx with 458752 (=7*65536) rows, and another table > -- salty, that is a copy of saltx > CREATE TABLE saltx > ( > AINT NO DEFAULT NOT NULL NOT DROPPABLE > SERIALIZED > , BINT NO DEFAULT NOT NULL NOT DROPPABLE > SERIALIZED > , CVARCHAR(20) CHARACTER SET ISO88591 > COLLATE > DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED > , PRIMARY KEY (A ASC, B ASC) > ) > SALT USING 4 PARTITIONS > ; > insert into saltx values (1,1,'hi there!'), > (2,1,'bye there!'),(3,1,'Happy Tuesday!'),(4,1,'Huckleberry Pie'); > insert into saltx select a+4,b,c from saltx; > insert into saltx select a+8,b,c from saltx; > insert into saltx select a+16,b,c from saltx; > insert into saltx select a+32,b,c from saltx; > insert into saltx select a+64,b,c from saltx; > insert into saltx select a+128,b,c from saltx; > insert into saltx select a+256,b,c from saltx; > insert into saltx select a+512,b,c from saltx; > insert into saltx select a+1024,b,c from saltx; > upsert into saltx select a+2048,b,c from saltx; > upsert into saltx select a+4096,b,c from saltx; > upsert into saltx select a+8192,b,c from saltx; > upsert into saltx select a+16384,b,c from saltx; > upsert into saltx select a+32768,b,c from saltx; > upsert using load into saltx select a,b+1,c from saltx; > upsert using load into saltx select a,b+2,c from saltx where b = 1; > upsert using load into saltx select a,b+3,c from saltx where b = 1; > upsert using load into saltx select a,b+4,c from saltx where b = 1; > upsert using load into saltx select a,b+5,c from saltx where b = 1; > upsert using load into saltx select a,b+6,c from saltx where b = 1; > update statistics for table saltx on every column; > create table salty like saltx; > upsert using load into salty select * from saltx; > update statistics for table salty on every column; > ?section deleteTest > set schema DeleteFailure; > set param ?b '4'; -- change it to '5' and the delete will succeed > prepare xx from delete from saltx where b > ?b; > explain options 'f' xx; > execute xx; -- fails with ungracious error message > Here is a log showing the deleteTest section failing: > [birdsall@dev02 IUDCosting]$ sqlci > Apache Trafodion Conversational Interface 1.3.0 > Copyright (c) 2015 Apache Software Foundation > >>obey deleteFailure.sql(deleteTest); > >>?section deleteTest > >> > >>set schema DeleteFailure; > --- SQL operation complete. > >> > >>set param ?b '4'; > >> -- change it to '5' and the delete will succeed > >> > >>prepare xx from delete from saltx where b > ?b; > --- SQL command prepared. > >> > >>explain options 'f' xx; > LC RC OP OPERATOR OPT DESCRIPTION CARD > - > 4.5rootx 1.52E+005 > 3.4esp_exchange1:4(hash2)1.52E+005 > 123tuple_flow1.52E+005 > ..2trafodion_vsbb_deletSALTX 1.00E+000 > ..1trafodion_scan SALTX 1.52E+005 > --- SQL operation complete. > >> > >>execute xx; > *** ERROR[8448] Unable to access Hbase interface. Call to > ExpHbaseInterface::nextRow returned error HBASE_ACCESS_ERROR(-706). Cause: > java.util.concurrent.ExecutionException: java.io.IOException: PerformScan > error on coprocessor call, scannerID: 14 java.io.IOException: performScan > encountered Exception txID: 70081 Exception: > org.apache.hadoop.hbase.exceptions.OutOfOrderScannerNextException: >
[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] [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] [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)
[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] [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=15422476#comment-15422476 ] liu ming commented on TRAFODION-2163: - I can reproduce the parallel issue. > 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-2493) to_char with format 'MONTH DD, YYYY, HH:MI' is wrong
[ https://issues.apache.org/jira/browse/TRAFODION-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2493: --- Assignee: Yang, Yongfeng (was: liu ming) > to_char with format 'MONTH DD, , HH:MI' is wrong > > > Key: TRAFODION-2493 > URL: https://issues.apache.org/jira/browse/TRAFODION-2493 > Project: Apache Trafodion > Issue Type: Bug > Components: dev-environment >Affects Versions: 2.0-incubating >Reporter: Yuan Liu >Assignee: Yang, Yongfeng > > SQL>select to_char(current_timestamp, 'MONTH DD, , HH:MI') from > (values(1)); > (EXPR) > - > February 21, 2017, 17:29: > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2493) to_char with format 'MONTH DD, YYYY, HH:MI' is wrong
[ https://issues.apache.org/jira/browse/TRAFODION-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2493: --- Assignee: liu ming > to_char with format 'MONTH DD, , HH:MI' is wrong > > > Key: TRAFODION-2493 > URL: https://issues.apache.org/jira/browse/TRAFODION-2493 > Project: Apache Trafodion > Issue Type: Bug > Components: dev-environment >Affects Versions: 2.0-incubating >Reporter: Yuan Liu >Assignee: liu ming > > SQL>select to_char(current_timestamp, 'MONTH DD, , HH:MI') from > (values(1)); > (EXPR) > - > February 21, 2017, 17:29: > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2483) Trafodion treat '\' as NULL in hive table
[
https://issues.apache.org/jira/browse/TRAFODION-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liu ming reassigned TRAFODION-2483:
---
Assignee: Yang, Yongfeng (was: liu ming)
> Trafodion treat '\' as NULL in hive table
> -
>
> Key: TRAFODION-2483
> URL: https://issues.apache.org/jira/browse/TRAFODION-2483
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: liu ming
>Assignee: Yang, Yongfeng
>
> If the source data in a hive table have '\', it will be mistakenly treated as
> NULL value ('\N').
> Not correct string comparing inside
> ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TRAFODION-2494) support listagg function
liu ming created TRAFODION-2494: --- Summary: support listagg function Key: TRAFODION-2494 URL: https://issues.apache.org/jira/browse/TRAFODION-2494 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming to simulate Oracle's listagg function. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2494) support listagg function
[ https://issues.apache.org/jira/browse/TRAFODION-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2494: --- Assignee: taian.wei > support listagg function > > > Key: TRAFODION-2494 > URL: https://issues.apache.org/jira/browse/TRAFODION-2494 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: taian.wei > > to simulate Oracle's listagg function. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TRAFODION-1861) support Trafodion running on CentOS 7
[ https://issues.apache.org/jira/browse/TRAFODION-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871103#comment-15871103 ] liu ming commented on TRAFODION-1861: - There is no expected release plan on this JIRA yet, this should not be one dependency for Trafodion 2.1 > support Trafodion running on CentOS 7 > - > > Key: TRAFODION-1861 > URL: https://issues.apache.org/jira/browse/TRAFODION-1861 > Project: Apache Trafodion > Issue Type: Umbrella > Components: Build Infrastructure, foundation, installer >Reporter: liu ming >Assignee: Eason Zhang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TRAFODION-2067) Support CDH 5.7
[ https://issues.apache.org/jira/browse/TRAFODION-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2067. - Resolution: Fixed > 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 > Fix For: 2.1-incubating > > > 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.15#6346)
[jira] [Resolved] (TRAFODION-2412) Add CREATE/DROP/ALTER SEQUENCE Statement + Update CREATE INDEX Statement
[ https://issues.apache.org/jira/browse/TRAFODION-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-2412. - Resolution: Fixed > Add CREATE/DROP/ALTER SEQUENCE Statement + Update CREATE INDEX Statement > > > Key: TRAFODION-2412 > URL: https://issues.apache.org/jira/browse/TRAFODION-2412 > Project: Apache Trafodion > Issue Type: Documentation >Reporter: liu ming >Assignee: Liu Yu > > add descriptions about how to use SEQUENCE and how to use IDENTITY column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2405) update sql reference manual about WITH clause syntax
[ https://issues.apache.org/jira/browse/TRAFODION-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2405: --- Assignee: Liu Yu (was: liu ming) > update sql reference manual about WITH clause syntax > > > Key: TRAFODION-2405 > URL: https://issues.apache.org/jira/browse/TRAFODION-2405 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: Liu Yu > > update syntax support of WITH clause -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TRAFODION-2405) update sql reference manual about WITH clause syntax
[ https://issues.apache.org/jira/browse/TRAFODION-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875602#comment-15875602 ] liu ming commented on TRAFODION-2405: - Trafodion can support ANSI SQL with-clause, so the documentation need to sync with it. Need to add description about syntax and usage examples, etc. > update sql reference manual about WITH clause syntax > > > Key: TRAFODION-2405 > URL: https://issues.apache.org/jira/browse/TRAFODION-2405 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: liu ming >Assignee: Liu Yu > > update syntax support of WITH clause -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TRAFODION-2483) Trafodion treat '\' as NULL in hive table
liu ming created TRAFODION-2483:
---
Summary: Trafodion treat '\' as NULL in hive table
Key: TRAFODION-2483
URL: https://issues.apache.org/jira/browse/TRAFODION-2483
Project: Apache Trafodion
Issue Type: Bug
Reporter: liu ming
Assignee: liu ming
If the source data in a hive table have '\', it will be mistakenly treated as
NULL value ('\N').
Not correct string comparing inside
ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (TRAFODION-2427) trafodion 2.0.1 install occurs an error ERROR: unable to find hbase-trx-cdh5_5-*.jar5-*.jar
[ https://issues.apache.org/jira/browse/TRAFODION-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827477#comment-15827477 ] liu ming commented on TRAFODION-2427: - Could you provide more information? Did you install CDH 5.5 first? Is it possible to paste all installation prompt options you entered during the installation? thanks. > trafodion 2.0.1 install occurs an error ERROR: unable to find > hbase-trx-cdh5_5-*.jar5-*.jar > --- > > Key: TRAFODION-2427 > URL: https://issues.apache.org/jira/browse/TRAFODION-2427 > Project: Apache Trafodion > Issue Type: Question > Components: installer >Reporter: jacklee > Labels: beginner > Fix For: 2.0-incubating > > > trafodion 2.0.1 install occurs an error > ***INFO: Cloudera installed will run traf_cloudera_mods > ***ERROR: unable to find > /usr/lib/trafodion/apache-trafodion_server-2.0.1-incubating/export/lib/hbase-trx-cdh5_5-*.jar > ***ERROR: traf_cloudera_mods exited with error. > ***ERROR: Please check log files. > ***ERROR: Exiting > help somebody help me,thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2443) update statistics gives a wrong error message
[ https://issues.apache.org/jira/browse/TRAFODION-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2443: Assignee: Yang, Yongfeng > update statistics gives a wrong error message > - > > Key: TRAFODION-2443 > URL: https://issues.apache.org/jira/browse/TRAFODION-2443 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Joshua Liu >Assignee: Yang, Yongfeng > > // below query is of bad syntax > SQL>update statistics for table timestamp_test1 on every column, (aa; > *** ERROR[9209] Column AA does not exist in object > TRAFODION.JOSH.TIMESTAMP_TEST1. [2017-01-12 08:26:01] > between, seems it tries to run the update statistics first, then try to check > the syntax... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2444) compile failed with 3 union alls
[ https://issues.apache.org/jira/browse/TRAFODION-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2444: --- Assignee: liu ming > compile failed with 3 union alls > > > Key: TRAFODION-2444 > URL: https://issues.apache.org/jira/browse/TRAFODION-2444 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Joshua Liu >Assignee: liu ming > Attachments: 三个union all编译出错，单独编译都能通过.msg > > > the sql is like: > -- > query1 > union all > query 2 > union all > query3 > -- > it compiled failed > but query1&2&3 can compile successfully respectively. > see attachment for more details... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2170) certain create table DDL will fail with core dump
liu ming created TRAFODION-2170: --- Summary: certain create table DDL will fail with core dump Key: TRAFODION-2170 URL: https://issues.apache.org/jira/browse/TRAFODION-2170 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming Assignee: liu ming create table test2170 ( c1 varchar(255) CHARACTER SET UTF8 not null, c2 varchar(256) CHARACTER SET UTF8 not null, c3 varchar(256) CHARACTER SET UTF8 not null, c4 int not null , c5 int, primary key(c1,c2,c3,c4)) salt using 4 partitions ; This will fail. -- 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=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] [Closed] (TRAFODION-2066) Not allowing Order By the aggregation, except when named
[ https://issues.apache.org/jira/browse/TRAFODION-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming closed TRAFODION-2066. --- Resolution: Duplicate dup with TRAFODION-2184 > Not allowing Order By the aggregation, except when named > > > Key: TRAFODION-2066 > URL: https://issues.apache.org/jira/browse/TRAFODION-2066 > Project: Apache Trafodion > Issue Type: Bug >Affects Versions: 2.1-incubating > Environment: EsgynDB Advanced Release 2.1.0 > JDBC Type 4, >Reporter: Yang Yang >Assignee: liu ming >Priority: Minor > Labels: newbie > > It's not allowed to Order By aggregates, unless a name is given to the > aggregate. For example, > Illegal to do "select id, groupid, sum(score) from t group by id, groupid > order by sum(score)". but it's legal to do "select id, groupid, sum(score) > as ttlscore from t group by id, groupid, order by ttlscore". > This may not be a problem with window functions. I've seen an example > Trafodion query: > "select username as userid,groupid,sum(allowed_size) as bandwidth, > row_number() over (partition by groupid order by SUM(allowed_size) desc) as > row_number from u_f-mv" . > This is not a blocking bug, but for those who'd like to test drive Trafodion, > the alternative of naming the aggregate may be put into SQL manual for now, > before the bug is fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2170) certain create table DDL will fail with core dump
[ https://issues.apache.org/jira/browse/TRAFODION-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15460108#comment-15460108 ] liu ming commented on TRAFODION-2170: - block on TRAFODION-2148 > certain create table DDL will fail with core dump > - > > Key: TRAFODION-2170 > URL: https://issues.apache.org/jira/browse/TRAFODION-2170 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > create table test2170 ( > c1 varchar(255) CHARACTER SET UTF8 not null, > c2 varchar(256) CHARACTER SET UTF8 not null, > c3 varchar(256) CHARACTER SET UTF8 not null, > c4 int not null , > c5 int, > primary key(c1,c2,c3,c4)) > salt using 4 partitions ; > This will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2063) SQL Errror 8102 occurred when down the region server
[ https://issues.apache.org/jira/browse/TRAFODION-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15460114#comment-15460114 ] liu ming commented on TRAFODION-2063: - there is potential race condition in sequence function, will need more time to investigate on this. > SQL Errror 8102 occurred when down the region server > > > Key: TRAFODION-2063 > URL: https://issues.apache.org/jira/browse/TRAFODION-2063 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Affects Versions: 2.0-incubating, 2.1-incubating > Environment: OS Type and Version: Centos release 6.7 > Trafodion SW Version: 2.1 > CDH Version: 5.5.4 > JDK Version: 1.7.0_67 >Reporter: Jarek >Assignee: liu ming > Attachments: > coast_2016-06-08_16.05.46.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log > > > Issue Description: > The following SQL Error 8102 occurred when down an region server. > "16:09:28 ***ERROR: SQLExecDirect: Expected: SQL_SUCCESS Actual: SQL_ERROR >File: ../../../../src/coast/coast_unified/src/jmtload.c Line: 187 >State: 23000 >Native Error: 4294959194 >Error: [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** > ERROR[8102] The operation is prevented by a unique constraint. [2016-06-08 > 16:09:28]" > > Steps: > Steps (cluster administrator page http://10.10.10.161:7180, username: admin, > password: admin) > Step 1. Enable High Availability in cluster testing environment. > Step 2. Run multi threads program that have connected to 32 mxosrsvr(s). > Step 3. Stop region server on centosha-5.novalocal node > Step 4. Check output of the multi threads program. > 1) output as below, > DEBUG: plan to delete total rows is 180385 > DEBUG: remaining rows to delete is 180296 > DEBUG: Remaining rows 310886 > DEBUG: Total rows 311000 > DEBUG: Deleted rows 89 > DEBUG: Missing insertion rows 25 # please note > the missing insertion rows because of the above error 8102. > Total Tests=1 Failed=1 > 2) log file attached, > “/opt/share/jarek/testing/odbc/builds_unix/coast/unified/linux64/coast_2016-06-08_16.05.46.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log”. > BTW, our table structure is below, and we can see the cache size is 25 that > is used to avoid concurrency conflict when insert data by multi threads > program, but it still occurred. > > SQL>showddl trafodion.j_schema_2.j_table_1; > > > CREATE TABLE TRAFODION.J_SCHEMA_2.J_TABLE_1 > ( > C0 LARGEINT GENERATED BY DEFAULT AS IDENTITY > ( START WITH 1 INCREMENT BY 1 MAXVALUE 9223372036854775806 MINVALUE > 1 >CACHE 25 NO CYCLE LARGEINT ) NOT NULL NOT DROPPABLE SERIALIZED > , C1 CHAR(20) CHARACTER SET ISO88591 COLLATE > DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED > , C2 INT NO DEFAULT SERIALIZED > , C3 SMALLINT NO DEFAULT NOT NULL NOT > DROPPABLE > SERIALIZED > , C4 DOUBLE PRECISION DEFAULT > -1.727233711019E-76 NOT SERIALIZED > , C5 DOUBLE PRECISION DEFAULT > -2.2250738585072014E-308 NOT NULL NOT DROPPABLE NOT SERIALIZED > , C6 DATE DEFAULT CURRENT NOT SERIALIZED > , C7 TIME(0) DEFAULT CURRENT NOT SERIALIZED > , C8 DECIMAL(18, 10) DEFAULT > 12345678.1234567890 NOT NULL NOT DROPPABLE NOT SERIALIZED > , C9 LARGEINT DEFAULT 9.223E18 SERIALIZED > , C10 NUMERIC(128, 0) DEFAULT > > 12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 > NOT NULL NOT DROPPABLE NOT SERIALIZED > , C11 REAL DEFAULT -1.1579208E38 NOT SERIALIZED > , C12 INTERVAL YEAR(5) TO MONTH DEFAULT NULL > NOT > SERIALIZED > , C13 CHAR(12) CHARACTER SET ISO88591 COLLATE > DEFAULT UPSHIFT DEFAULT _ISO88591'defaULT' SERIALIZED > , C14 CHAR(8) CHARACTER SET ISO88591 COLLATE > DEFAULT DEFAULT _ISO88591'summer' SERIALIZED > , C15 VARCHAR(10) CHARACTER SET ISO88591 > COLLATE > DEFAULT DEFAULT _ISO88591'china' SERIALIZED > , CTIMESTAMP(6) DEFAULT CURRENT NOT > SERIALIZED > , PRIMARY KEY (C0 ASC) > ) > ; > > -- The following sequence is a system created sequence -- > > CREATE SEQUENCE TRAFODION.J_SCHEMA_2."_TRAFODION_J_SCHEMA_2_J_TABLE_1_C0_" /* > INTERNAL */ > START WITH 1 /* NEXT AVAILABLE VALUE 311001 */
