[jira] [Created] (TRAFODION-1796) Executor TEST131 fails with does not exist or is inaccessible error

2016-02-01 Thread Roberta Marton (JIRA) 
Roberta Marton created TRAFODION-1796:
-

 Summary: Executor TEST131 fails with  does not exist or is 
inaccessible error
 Key: TRAFODION-1796
 URL: https://issues.apache.org/jira/browse/TRAFODION-1796
 Project: Apache Trafodion
  Issue Type: Test
  Components: sql-general
Reporter: Roberta Marton


Executor TEST131 is failing even though the table exists:

 *** ERROR[4082] Object TRAFODION.SEABASE.T1311K does not exist or is 
inaccessible.

Executor TEST131, which runs in sqlci (main sqlci) starts up a second sqlci 
(secondary sqlci) to run some queries.  The main sqlci creates the tables and 
the secondary sqlci tries to access them.  The secondary sqlci is failing with 
error 4082 when it tries to access tables created by the main sqlci.

Background: the runregr_executor.ksh script which controls the regression test 
obeys a file called cidefs prior to running the test queries.  cidefs sets up 
common information needed by the tests tests. cidefs contains the following 
statement (among others):

   set SCHEMA $$TEST_SCHEMA$$;

In this case, TEST_SCHEMA is equivalent to trafodion.sch.  So the main sqlci 
session assumes that the default schema is trafodion.sch.

When the second sqlci session starts, it uses the default schema that is set by 
default in the system.  In this case, the default schema happens to be 
trafodion.seabase. (During “initialize trafodion”, the software creates this 
schema and makes it the default.)

So queries fail in the secondary sqlci session because it is looking in the 
wrong schema.

So how did this ever work?

A special test exists in the core test suite – core/TEST000 that creates a 
bunch of default information.  One of the statements changes the default schema 
from trafodion.seabase to trafodion.sch (through an insert into the 
“_MD_”.defaults table). So, if you run core/TEST000, as recommended, before 
running executor/TEST131, the test passes.  In this case, the second sqlci 
session uses trafodion.sch as the default schema.  This matches what the main 
sqlci session uses.

To avoid having TEST131 fail in our daily runs,   TEST131 will be updated.  
However, a long term solution is needed so other can avoid this problem.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1796) Executor TEST131 fails with does not exist or is inaccessible error

2016-02-01 Thread David Wayne Birdsall (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127053#comment-15127053
 ] 

David Wayne Birdsall commented on TRAFODION-1796:
-

Actually, this clears up a mystery for me. I've noticed that on a workstation, 
sometimes the default schema is SCH, and sometimes SEABASE. I had wondered why. 
It seems it is a matter of whether I've run the executor/TEST000 regression 
test.

Changing the default in a global way seems unfriendly to me. If I'm doing other 
work in parallel with a regression test run, the last thing I want is the 
default schema to change underneath me.


> Executor TEST131 fails with  does not exist or is inaccessible error
> ---
>
> Key: TRAFODION-1796
> URL: https://issues.apache.org/jira/browse/TRAFODION-1796
> Project: Apache Trafodion
>  Issue Type: Test
>  Components: sql-general
>Reporter: Roberta Marton
>
> Executor TEST131 is failing even though the table exists:
>  *** ERROR[4082] Object TRAFODION.SEABASE.T1311K does not exist or is 
> inaccessible.
> Executor TEST131, which runs in sqlci (main sqlci) starts up a second sqlci 
> (secondary sqlci) to run some queries.  The main sqlci creates the tables and 
> the secondary sqlci tries to access them.  The secondary sqlci is failing 
> with error 4082 when it tries to access tables created by the main sqlci.
> Background: the runregr_executor.ksh script which controls the regression 
> test obeys a file called cidefs prior to running the test queries.  cidefs 
> sets up common information needed by the tests tests. cidefs contains the 
> following statement (among others):
>set SCHEMA $$TEST_SCHEMA$$;
> In this case, TEST_SCHEMA is equivalent to trafodion.sch.  So the main sqlci 
> session assumes that the default schema is trafodion.sch.
> When the second sqlci session starts, it uses the default schema that is set 
> by default in the system.  In this case, the default schema happens to be 
> trafodion.seabase. (During “initialize trafodion”, the software creates this 
> schema and makes it the default.)
> So queries fail in the secondary sqlci session because it is looking in the 
> wrong schema.
> So how did this ever work?
> A special test exists in the core test suite – core/TEST000 that creates a 
> bunch of default information.  One of the statements changes the default 
> schema from trafodion.seabase to trafodion.sch (through an insert into the 
> “_MD_”.defaults table). So, if you run core/TEST000, as recommended, before 
> running executor/TEST131, the test passes.  In this case, the second sqlci 
> session uses trafodion.sch as the default schema.  This matches what the main 
> sqlci session uses.
> To avoid having TEST131 fail in our daily runs,   TEST131 will be updated.  
> However, a long term solution is needed so other can avoid this problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1749) Unable to build or run Trafodion because of missing log4cxx files

2016-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126791#comment-15126791
 ] 

ASF GitHub Bot commented on TRAFODION-1749:
---

GitHub user svarnau opened a pull request:

https://github.com/apache/incubator-trafodion/pull/298

[TRAFODION-1749] Bundle log4cxx library in Trafodion build

Since log4cxx is not available in all Linux distros, we make it a
build-time dependency only, and bundle the shared library for runtime.
This eliminates the installer dependency to check log4cxx package.

The build-time dependency can be satisfied either by installing log4cxx
and log4cxx-devel RPM packages, if available, or by building library
from source.  The traf_tools_setup.sh script is enhanced to download
source code and build this dependency.

@robertamarton @amandamoran 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/svarnau/incubator-trafodion log4cxx

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafodion/pull/298.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #298


commit 7c37f1ae23e62e5f4cc4caa12518b613b62c7583
Author: Steve Varnau 
Date:   2016-02-01T18:40:33Z

[TRAFODION-1749] Bundle log4cxx library in Trafodion build

Since log4cxx is not available in all Linux distros, we make it a
build-time dependency only, and bundle the shared library for runtime.
This eliminates the installer dependency to check log4cxx package.

The build-time dependency can be satisfied either by installing log4cxx
and log4cxx-devel RPM packages, if available, or by building library
from source.  The traf_tools_setup.sh script is enhanced to download
source code and build this dependency.




> Unable to build or run Trafodion because of missing log4cxx files
> -
>
> Key: TRAFODION-1749
> URL: https://issues.apache.org/jira/browse/TRAFODION-1749
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: Build Infrastructure
>Reporter: Roberta Marton
>Assignee: Steve Varnau
> Attachments: log4cxx-0.10.0-13.fc18.src.rpm, 
> log4cxx-devel-0.10.0-13.el6.x86_64.rpm
>
>
> Recently, the log4cxx libraries are been removed from download repositories 
> such as YUM and EPEL.  Without these libraries, Trafodion cannot be built or 
> run.
> A solution is needed to fix this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1757) Imporovements to install traf components

2016-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127033#comment-15127033
 ] 

ASF GitHub Bot commented on TRAFODION-1757:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/293


> Imporovements to install traf components
> 
>
> Key: TRAFODION-1757
> URL: https://issues.apache.org/jira/browse/TRAFODION-1757
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: connectivity-general
>Reporter: Anuradha Hegde
>Assignee: Anuradha Hegde
>
> Missing linux driver dsn configuration  and odb support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TRAFODION-1798) Support Transactions for DDL statements

2016-02-01 Thread Prashanth Vasudev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashanth Vasudev updated TRAFODION-1798:
-
Attachment: TransactionsDDL_Apache.pdf

Attached is the initial design that was performed to support this feature.


> Support Transactions for DDL statements
> ---
>
> Key: TRAFODION-1798
> URL: https://issues.apache.org/jira/browse/TRAFODION-1798
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: Prashanth Vasudev
>Assignee: Prashanth Vasudev
> Attachments: TransactionsDDL_Apache.pdf
>
>
> This work to support transaction for DDL operations started before Trafodion 
> became part of incubation as Apache Trafodion.  The initial link to the 
> blueprint is https://blueprints.launchpad.net/trafodion/+spec/dtm-ddl-support
> Some of the implementation to support this feature is already in code base, 
> however there are some more additional changes needed to support completely.
> Additional changes include:
> 1. SQL executor changes to leverage transactional DDL support by transaction 
> manager.
> 2. Issue with simultaneous transactional update to the table followed by 
> drop. This manifests as a hang when a drop schema is performed.
> 3. Recovery in case of HA failure scenario.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (TRAFODION-1791) UPSERT with bare one row subquery in VALUES clause fails

2016-02-01 Thread Suresh Subbiah (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suresh Subbiah resolved TRAFODION-1791.
---
Resolution: Fixed

> UPSERT with bare one row subquery in VALUES clause fails
> 
>
> Key: TRAFODION-1791
> URL: https://issues.apache.org/jira/browse/TRAFODION-1791
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.2-incubating
>Reporter: Suresh Subbiah
>Assignee: Suresh Subbiah
> Fix For: 2.0-incubating
>
>
> When a table with an index is upserted into using a statement of this form
> UPSERT INTO  VALUES(...);
> we get a compiler error in the generator phase with error code 7000.
> CREATE TABLE DEC
> (
> ID int unsigned GENERATED BY DEFAULT AS IDENTITY (CACHE 5000) NOT NULL,
> codeValue varchar(1000),
> title varchar(100),
> shortName varchar(200),
> description varchar(1000),
> path varchar(1000),
> synonyms varchar(1000),
> objectClassCode varchar(100),
> propertyCode varchar(100),
> PRIMARY KEY (ID)
> );
> CREATE INDEX IDX3_DEC_T_CodeValue ON DEC(codeValue);
> CREATE TABLE DE
> (
> ID int unsigned GENERATED BY DEFAULT AS IDENTITY (CACHE 5000) NOT NULL,
> dataElementConceptID int unsigned,
> valueDomainID int unsigned,
> PRIMARY KEY (ID)
> );
> ALTER TABLE DE
> ADD CONSTRAINT FK1_DE_DEC
> FOREIGN KEY (dataElementConceptID)
> REFERENCES DEC(ID);
> CREATE INDEX IDX1_DE ON DE(dataElementConceptID, valueDomainID);
> --- gives error 7000
> prepare s9 from UPSERT INTO DE (ID, dataElementConceptID, valueDomainID)  
> VALUES  (1,  (select d.id from DEC d where d.codeValue = 'aa'),  3 ) ;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TRAFODION-1797) Provide a REST interface to obtain DCS master configuration

2016-02-01 Thread Venkat Muthuswamy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Venkat Muthuswamy updated TRAFODION-1797:
-
Description: The current REST APIs lets us know the number of configured 
DCS masters and mxosrvrs. But we dont know if DCS is configured for HA. What is 
the primary DCS master and the backup masters and which DCS master is active. A 
REST API to provide this information will be useful.

> Provide a REST interface to obtain DCS master configuration
> ---
>
> Key: TRAFODION-1797
> URL: https://issues.apache.org/jira/browse/TRAFODION-1797
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Venkat Muthuswamy
>Assignee: Venkat Muthuswamy
>
> The current REST APIs lets us know the number of configured DCS masters and 
> mxosrvrs. But we dont know if DCS is configured for HA. What is the primary 
> DCS master and the backup masters and which DCS master is active. A REST API 
> to provide this information will be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1726) DatabaseMetaData.getIndexInfo does not work

2016-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127148#comment-15127148
 ] 

ASF GitHub Bot commented on TRAFODION-1726:
---

Github user arvind-narain commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/243#discussion_r51490240
  
--- Diff: core/conn/jdbc_type2/native/SrvrCommon.cpp ---
@@ -1634,6 +1635,53 @@ short do_ExecSMD(
 tableParam[0], inputParam[0], inputParam[1],
 inputParam[2], inputParam[3]);
 break;
+   case SQL_API_SQLSTATISTICS:
+   if ((!checkIfWildCard(catalogNm, catalogNmNoEsc) || 
!checkIfWildCard(schemaNm, schemaNmNoEsc)
+   || !checkIfWildCard(tableNm, tableNmNoEsc)) && 
!metadataId)
+   {
+   executeException->exception_nr = 
odbc_SQLSvc_GetSQLCatalogs_ParamError_exn_;
+   executeException->u.ParamError.ParamDesc = 
SQLSVC_EXCEPTION_WILDCARD_NOT_SUPPORTED;
+   
FUNCTION_RETURN_NUMERIC(EXECUTE_EXCEPTION,("EXECUTE_EXCEPTION"));
+   }
+
+   if (strcmp(catalogNm,"") == 0)
+   strcpy(tableName1,SEABASE_MD_CATALOG);
+   else
+   strcpy(tableName1, catalogNm);
+   tableParam[0] = tableName1;
+   convertWildcard(metadataId, TRUE, schemaNm, expSchemaNm);
+   convertWildcardNoEsc(metadataId, TRUE, schemaNm, 
schemaNmNoEsc);
+   convertWildcard(metadataId, TRUE, tableNm, expTableNm);
+   convertWildcardNoEsc(metadataId, TRUE, tableNm, 
tableNmNoEsc);
+   if( inputParam[5] != NULL )
+   {
+   sprintf(cunique, " and index.IS_UNIQUE=1");
+   }
+   inputParam[0] = schemaNmNoEsc;
+   inputParam[1] = expSchemaNm;
+   inputParam[2] = tableNmNoEsc;
+   inputParam[3] = expTableNm;
+   inputParam[4] = NULL;
+   snprintf((char *)sqlString->dataValue._buffer, totalSize,
+   "select "
+   "obj.CATALOG_NAME TABLE_CAT, obj.SCHEMA_NAME TABLE_SCHEM, 
obj.OBJECT_NAME TABLE_NAME,"
+   "cast((case when index.IS_UNIQUE=0 then 1 else 0 end) as 
smallint) NON_UNIQUE, "
+   "cast(NULL as varchar(32)) INDEX_QUALIFIER, 
idxobj.OBJECT_NAME INDEX_NAME, "
+   "cast(-2 as smallint) TYPE, cols.COLUMN_NUMBER 
ORDINAL_POSITION, "
+   "substr(cols.COLUMN_NAME,0,CHAR_LENGTH(cols.COLUMN_NAME)) 
COLUMN_NAME, "
+   "cast((case when keys.ORDERING=0 then 'A' else 'D' end) as 
varchar(4)) ASC_OR_DESC,"
+   "cast(-2 as int) CARDINALITY, cast(-2 as int) PAGES, 
cast(NULL as varchar(10)) FILTER_CONDITION "
--- End diff --

1. Sorry for the confusion and the delay Kevin. I was referring to the 
output when all tables (%) under a schema are specified. In my testing the 
query in the code returned some rows with empty index name and in some cases 
temporary table names etc. This can be fixed in a separate JIRA if needed.

 
   TRAFODION
   MTD
   MTD0
   0
   NULL
   NULL
   -2
   NULL
   NULL
   D
   -2
   -2
   NULL
 
 
   TRAFODION
   MTD
   __SCHEMA__
   0
   NULL
   NULL
   -2
   NULL
   NULL
   D
   -2
   -2
   NULL
 

2. I did look at the corresponding ODBC API. Ordinal position should start 
from 1, so please fix this one and I'll check this in. The following should be 
changed -

 cols.COLUMN_NUMBER ORDINAL_POSITION

to

   keys.KEYSEQ_NUMBER ORDINAL_POSITION

or with a cast if needed.

3. Also could you please create a separate enhancement JIRA - I think for  
column_class 'S' -  "DIVISION BY" column_name (_DIVISION_n) and SALT we  should 
have an optional column at the end - maybe "REMARKS" or some appropriate 
heading which should give the text from text.text - null for non-system columns 
(column_class <> 'S')


> DatabaseMetaData.getIndexInfo does not work
> ---
>
> Key: TRAFODION-1726
> URL: https://issues.apache.org/jira/browse/TRAFODION-1726
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-jdbc-t2
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> DatabaseMetaData.getIndexInfo("TRAFODION", "SEABASE", "OSD28DL_Z1", false, 
> true)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1798) Support Transactions for DDL statements

2016-02-01 Thread Prashanth Vasudev (JIRA) 
Prashanth Vasudev created TRAFODION-1798:


 Summary: Support Transactions for DDL statements
 Key: TRAFODION-1798
 URL: https://issues.apache.org/jira/browse/TRAFODION-1798
 Project: Apache Trafodion
  Issue Type: New Feature
Reporter: Prashanth Vasudev


This work to support transaction for DDL operations started before Trafodion 
became part of incubation as Apache Trafodion.  The initial link to the 
blueprint is https://blueprints.launchpad.net/trafodion/+spec/dtm-ddl-support

Some of the implementation to support this feature is already in code base, 
however there are some more additional changes needed to support completely.
Additional changes include:

1. SQL executor changes to leverage transactional DDL support by transaction 
manager.
2. Issue with simultaneous transactional update to the table followed by drop. 
This manifests as a hang when a drop schema is performed.
3. Recovery in case of HA failure scenario.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (TRAFODION-1797) Provide a REST interface to obtain DCS master configuration

2016-02-01 Thread Venkat Muthuswamy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on TRAFODION-1797 started by Venkat Muthuswamy.

> Provide a REST interface to obtain DCS master configuration
> ---
>
> Key: TRAFODION-1797
> URL: https://issues.apache.org/jira/browse/TRAFODION-1797
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Venkat Muthuswamy
>Assignee: Venkat Muthuswamy
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1705) JVM crashes when trying to populate Trafodion table with a long key

2016-02-01 Thread Suresh Subbiah (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127283#comment-15127283
 ] 

Suresh Subbiah commented on TRAFODION-1705:
---

I am seeing a similar problem when a table has a long (> 1000 bytes) key. 
Tables lineitem and lineitem1 cause sqlci to crash. If sqlci is in gdb I saw 
this in the stack (higher stack is in JNI)
Table lineitem2 has a smaller key (since a char(255) column is declared as 
ISO88591 instead of UTF8) and does not have this problem.
An index is used here, but for table lineitem, I dropped the index, inserted 1 
row (does not use TM) and then got the same error when I tried to delete all 
rows from the table (uses TM)
 
#16 0x7023e15f in TM_Transaction::register_region (this=0x2540810, 
startid=-1, port=47972, hostName=
0x7ffed630 "\377\177", hostname_Length=538976288, 
startcode=2314885530818453536, regionInfo=
0xbbf0007fff , 
regionInfo_Length=0) at tmtransaction.cpp:113

create schema tp;
set schema tp;
CREATE TABLE TRAFODION.TP.LINEITEM
  (
L_ORDERKEY INT DEFAULT NULL SERIALIZED
  , L_PARTKEY INT DEFAULT NULL SERIALIZED
  , L_SUPPKEY INT DEFAULT NULL SERIALIZED
  , L_LINENUMBER INT DEFAULT NULL SERIALIZED
  , L_QUANTITY DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_EXTENDEDPRICE DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_DISCOUNT DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_TAX DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_RETURNFLAG VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_LINESTATUS VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_SHIPDATE TIMESTAMP(6) NO DEFAULT NOT NULL NOT
  DROPPABLE NOT SERIALIZED
  , L_COMMITDATE TIMESTAMP(6) DEFAULT NULL NOT SERIALIZED
  , L_RECEIPTDATE TIMESTAMP(6) DEFAULT NULL NOT SERIALIZED
  , L_SHIPINSTRUCT VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  , L_SHIPMODE VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  , L_COMMENT VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  )
  STORE BY (L_SHIPDATE ASC, L_LINESTATUS ASC, L_RETURNFLAG ASC)
  SALT USING 4 PARTITIONS
; 
create index l_discount_idx on lineitem (L_ORDERKEY ) salt like table;
insert into lineitem values (1,1,1,1,1,1,1,1,'a','a',timestamp '1997-01-01 
21:11:52.145',timestamp '1997-01-01 21:11:52.145',timestamp '1997-01-01 
21:11:52.145','a','a','a');

CREATE TABLE TRAFODION.TP.LINEITEM2
  (
L_ORDERKEY INT DEFAULT NULL SERIALIZED
  , L_PARTKEY INT DEFAULT NULL SERIALIZED
  , L_SUPPKEY INT DEFAULT NULL SERIALIZED
  , L_LINENUMBER INT DEFAULT NULL SERIALIZED
  , L_QUANTITY DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_EXTENDEDPRICE DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_DISCOUNT DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_TAX DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_RETURNFLAG VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_LINESTATUS VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_SHIPDATE TIMESTAMP(6) NO DEFAULT NOT NULL NOT
  DROPPABLE NOT SERIALIZED
  , L_COMMITDATE TIMESTAMP(6) DEFAULT NULL NOT SERIALIZED
  , L_RECEIPTDATE TIMESTAMP(6) DEFAULT NULL NOT SERIALIZED
  , L_SHIPINSTRUCT VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  , L_SHIPMODE VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  , L_COMMENT VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT DEFAULT NULL SERIALIZED
  )
  STORE BY (L_SHIPDATE ASC, L_LINESTATUS ASC)
  SALT USING 4 PARTITIONS
; 

create index l_discount_idx2 on lineitem2 (L_ORDERKEY );

insert into lineitem2 values (1,1,1,1,1,1,1,1,'a','a',timestamp '1997-01-01 
21:11:52.145',timestamp '1997-01-01 21:11:52.145',timestamp '1997-01-01 
21:11:52.145','a','a','a');

CREATE TABLE TRAFODION.TP.LINEITEM3
  (
L_ORDERKEY INT DEFAULT NULL SERIALIZED
  , L_PARTKEY INT DEFAULT NULL SERIALIZED
  , L_SUPPKEY INT DEFAULT NULL SERIALIZED
  , L_LINENUMBER INT DEFAULT NULL SERIALIZED
  , L_QUANTITY DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_EXTENDEDPRICE DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_DISCOUNT DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_TAX DOUBLE PRECISION DEFAULT NULL NOT
  SERIALIZED
  , L_RETURNFLAG VARCHAR(255 CHARS) CHARACTER SET UTF8
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_LINESTATUS VARCHAR(255 CHARS) CHARACTER SET ISO88591
  COLLATE DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , L_SHIPDATE TIMESTAMP(6) NO DEFAULT NOT NULL NOT
  DROPPABLE NOT SERIALIZED

[jira] [Created] (TRAFODION-1797) Provide a REST interface to obtain DCS master configuration

2016-02-01 Thread Venkat Muthuswamy (JIRA) 
Venkat Muthuswamy created TRAFODION-1797:


 Summary: Provide a REST interface to obtain DCS master 
configuration
 Key: TRAFODION-1797
 URL: https://issues.apache.org/jira/browse/TRAFODION-1797
 Project: Apache Trafodion
  Issue Type: Improvement
Reporter: Venkat Muthuswamy






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (TRAFODION-1798) Support Transactions for DDL statements

2016-02-01 Thread Prashanth Vasudev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on TRAFODION-1798 started by Prashanth Vasudev.

> Support Transactions for DDL statements
> ---
>
> Key: TRAFODION-1798
> URL: https://issues.apache.org/jira/browse/TRAFODION-1798
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: Prashanth Vasudev
>Assignee: Prashanth Vasudev
>
> This work to support transaction for DDL operations started before Trafodion 
> became part of incubation as Apache Trafodion.  The initial link to the 
> blueprint is https://blueprints.launchpad.net/trafodion/+spec/dtm-ddl-support
> Some of the implementation to support this feature is already in code base, 
> however there are some more additional changes needed to support completely.
> Additional changes include:
> 1. SQL executor changes to leverage transactional DDL support by transaction 
> manager.
> 2. Issue with simultaneous transactional update to the table followed by 
> drop. This manifests as a hang when a drop schema is performed.
> 3. Recovery in case of HA failure scenario.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TRAFODION-1705) JVM crashes when trying to populate Trafodion table with a long key

2016-02-01 Thread Jian Jin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jian Jin updated TRAFODION-1705:

Assignee: mashengchen

> JVM crashes when trying to populate Trafodion table with a long key
> ---
>
> Key: TRAFODION-1705
> URL: https://issues.apache.org/jira/browse/TRAFODION-1705
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dtm
>Affects Versions: 2.0-incubating, 1.3-incubating
> Environment: I encountered this problem on a workstation, but I 
> expect it will happen anywhere.
>Reporter: David Wayne Birdsall
>Assignee: mashengchen
>
> The following script run in sqlci produces a JVM crash:
> ?section createit
> CREATE TABLE  t807e
> (
> C1 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C2 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C3 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C4 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C5 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C6 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C7 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C8 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C9 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C10 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C11 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C12 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C13 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C14 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C15 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C16 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C17 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C18 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C19 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C215 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' NOT NULL NOT DROPPABLE SERIALIZED
> , C300 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C301 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C302 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C303 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C304 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C305 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C306 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C307 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C308 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C309 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C310 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C311 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C312 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C313 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C314 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C315 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C316 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C317 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C318 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C319 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C320 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C321 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C322 VARCHAR(50 CHARS) CHARACTER SET UTF8
> COLLATE DEFAULT DEFAULT _UTF8'' SERIALIZED
> , C323 VARCHAR(50 CHARS) CHARACTER SET UTF8
>

[jira] [Commented] (TRAFODION-1699) Trafodion web site requires additional work

2016-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127315#comment-15127315
 ] 

ASF GitHub Bot commented on TRAFODION-1699:
---

GitHub user svarnau opened a pull request:

https://github.com/apache/incubator-trafodion/pull/300

[TRAFODION-1699] Expose in-development manuals on documentation web page

Also fix URL of the 1.3 API docs.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/svarnau/incubator-trafodion docs2.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafodion/pull/300.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #300


commit b5860dce0313fc2030a1617cadbf8788307a43c7
Author: Steve Varnau 
Date:   2016-02-02T00:10:56Z

Expose in-development manuals on documentation web page

Also fix URL of the 1.3 API docs.




> Trafodion web site requires additional work
> ---
>
> Key: TRAFODION-1699
> URL: https://issues.apache.org/jira/browse/TRAFODION-1699
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.0-incubating
>Reporter: Gunnar Tapper
>Assignee: Gunnar Tapper
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1703) Lower overhead in deleting old Tlog entries

2016-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126569#comment-15126569
 ] 

ASF GitHub Bot commented on TRAFODION-1703:
---

Github user DaveBirdsall commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/296#discussion_r51445704
  
--- Diff: 
core/sqf/src/seatrans/hbase-trx/src/main/java/org/apache/hadoop/hbase/coprocessor/transactional/generated/TrxRegionProtos.java
 ---
@@ -26558,6 +26558,16 @@ public Builder clearHasException() {
  * required int64 auditSeqNum = 4;
  */
 long getAuditSeqNum();
+
+// required bool ageCommitted = 5;
+/**
+ * required bool ageCommitted = 5;
+ */
+boolean hasAgeCommitted();
+/**
+ * required bool ageCommitted = 5;
--- End diff --

What is the point of the repeated required bool ageCommitted = 
5; comments? There seems to be several of them.


> Lower overhead in deleting old Tlog entries
> ---
>
> Key: TRAFODION-1703
> URL: https://issues.apache.org/jira/browse/TRAFODION-1703
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: dtm
>Affects Versions: 1.3-incubating
>Reporter: Sean Broeder
>Assignee: Sean Broeder
> Fix For: 1.3-incubating
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently, Tlog entries are maintained for a period of time when there is a 
> chance they might be needed to help recover from some sort of failure.  After 
> that widow expires the old records can be deleted.
> The current mechanism starts a scanner on the region which sends every record 
> to the client Tlog component where the record is evaluated and if the 
> deletion criteria are met a Delete is created and sent back to the region.  
> This creates a lot of unnecessary message traffic since none of the contents 
> of the record is actually needed by the Tlog component during the maintenance 
> operation.
> It would be better to send the deletion criteria to the region so that the 
> region itself to perform the necessary housekeeping without sending all the 
> data back to the client Tlog component.
> I believe the endpoint coprocessor service could be used to perform this work.
> Comments?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (TRAFODION-1745) show more related info when TRANSLATE run into SQL Error

2016-02-01 Thread liu ming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on TRAFODION-1745 started by liu ming.
---
> show more related info when TRANSLATE run into SQL Error
> 
>
> Key: TRAFODION-1745
> URL: https://issues.apache.org/jira/browse/TRAFODION-1745
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: liu ming
>Assignee: liu ming
>
> The current error message for a TRANSLATE error can be :
> 8690 "An invalid character value encountered in TRANSLATE function."
> Need to show more helping info for easier debug, and user friendly.
> to include a short section of offending source data (may be in hex form), 
> source charset, and target charset.
> Checking other SQL errors related if possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-1797) Provide a REST interface to obtain DCS master configuration

2016-02-01 Thread Venkat Muthuswamy (JIRA) 

[ 
https://issues.apache.org/jira/browse/TRAFODION-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127687#comment-15127687
 ] 

Venkat Muthuswamy commented on TRAFODION-1797:
--

The dcscheck script displays the dcs summary information. It tells us if DCS is 
configured in HA mode, it tells the primary and backup DCS masters and which 
node is running the active dcs master. Using the REST server script interface, 
this can be exposed as a JSON response.

> Provide a REST interface to obtain DCS master configuration
> ---
>
> Key: TRAFODION-1797
> URL: https://issues.apache.org/jira/browse/TRAFODION-1797
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Venkat Muthuswamy
>Assignee: Venkat Muthuswamy
>
> The current REST APIs lets us know the number of configured DCS masters and 
> mxosrvrs. But we dont know if DCS is configured for HA. What is the primary 
> DCS master and the backup masters and which DCS master is active. A REST API 
> to provide this information will be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (TRAFODION-1720) add GBK support in SQL translate function

2016-02-01 Thread liu ming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liu ming resolved TRAFODION-1720.
-
Resolution: Fixed

merged into github

> add GBK support in SQL translate function
> -
>
> Key: TRAFODION-1720
> URL: https://issues.apache.org/jira/browse/TRAFODION-1720
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Reporter: liu ming
>Assignee: liu ming
>
> Trafodion support TRANSLATE function now and support character set conversion 
> among ISO88591, SJIS, UCS2 and UTF8. It will be useful to support GBK and 
> later BIG5.
> GBK is widely used in China. Without support, all source data need to be 
> converted before data loading. With built-in support, it will decrease the 
> overall data loading time.
> External interface
> Use the current SQL Function TRANSLATE, introduce new translation, keep the 
> original syntax.
>  
> TRANSLATE(character-value-expression USING translation-name)
> Translation-name  Source charset  Target charset  Comments
> == ==     =
>   GBKTOUTF8  GBK2312  UTF8When error occur during 
> translation, SQL Error
> UTF8TOGBK UTF8GB2312
> Internal
> Parser change
> Let class Translate support new translation-name.
> CodeGen change
> Translate::codeGen
> Executor change
> convDoIt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)