date:20160509

[jira] [Commented] (TRAFODION-1978) Skip LOB columns for UPDATE STATS

2016-05-09 Thread ASF GitHub Bot (JIRA)


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

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

Github user asfgit closed the pull request at:

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


> Skip LOB columns for UPDATE STATS
> -
>
> Key: TRAFODION-1978
> URL: https://issues.apache.org/jira/browse/TRAFODION-1978
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
>
> As shown below, update stats currently does not work for LOB columns. This 
> case is filed to track this issue. In the long run, we perhaps should 
> consider supporting update stats on LOB data types. In the short run, we 
> should make it return better error messages. The current error messages are 
> all over the map with lots of internal references.
> This was seen on the AdvEnt2.1 v0419 build installed on a 4-node cluster.
> >>control query default TRAF_BLOB_AS_VARCHAR 'OFF';
> --- SQL operation complete.
> >>control query default TRAF_CLOB_AS_VARCHAR 'OFF';
> --- SQL operation complete.
> >>
> >>create schema mytest;
> --- SQL operation complete.
> >>set schema mytest;
> --- SQL operation complete.
> >>
> >>create table mytable (row_id int, c1 blob, c2 clob);
> --- SQL operation complete.
> >>
> >>insert into table mytable values (1, stringtolob('string 1'), 
> >>stringtolob('string 2'));
> --- 1 row(s) inserted.
> >>
> >>insert into table mytable values (2, stringtolob('string 3'), 
> >>stringtolob('string 4'));
> --- 1 row(s) inserted.
> >>
> >>insert into table mytable values (3, stringtolob('string 5'), 
> >>stringtolob('string 6'));
> --- 1 row(s) inserted.
> >>
> >>update statistics for table mytable on (c1);
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement HSCursor::prepareRowsetInternal().
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement FETCH_BOUNDARY_ROWSET.
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> >>update statistics for table mytable on (c2);
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement HSCursor::prepareRowsetInternal().
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement FETCH_BOUNDARY_ROWSET.
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> >>update statistics for table mytable on every column;
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement HSCursor::prepareRowsetInternal().
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> *** ERROR[9200] UPDATE STATISTICS for table TRAFODION.MYTEST.MYTABLE 
> encountered an error (4322) from statement FETCH_BOUNDARY_ROWSET.
> *** ERROR[4322] A column with BLOB datatype cannot be used in this clause or 
> function.
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> Here is the entire script to reproduce this problem:
> control query default TRAF_BLOB_AS_VARCHAR 'OFF';
> control query default TRAF_CLOB_AS_VARCHAR 'OFF';
> create schema mytest;
> set schema mytest;
> create table mytable (row_id int, c1 blob, c2 clob);
> insert into table mytable values (1, stringtolob('string 1'), 
> stringtolob('string 2'));
> insert into table mytable values (2, stringtolob('string 3'), 
> stringtolob('string 4'));
> insert into table mytable values (3, stringtolob('string 5'), 
> stringtolob('string 6'));
> update statistics for table mytable on (c1);
> update statistics for table mytable on (c2);
> update statistics for table mytable on every column;
> drop schema mytest cascade;



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

[jira] [Created] (TRAFODION-1986) trafodion jdbc t4 api can't set schema

2016-05-09 Thread mashengchen (JIRA)

mashengchen created TRAFODION-1986:
--

 Summary: 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


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] [Commented] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

2016-05-09 Thread ASF GitHub Bot (JIRA)


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

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

GitHub user zellerh opened a pull request:

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

TRAFODION-1983 error in preCodeGen plus more items

This also constains a fix for TRAFODION-1710 (setString in UDFs does not 
accept numeric values with scale) as well as misc small fixes. It may make more 
sense to review the three commits in this PR separately, as they are on 
different topics.

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

$ git pull https://github.com/zellerh/incubator-trafodion bug/1910

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

https://github.com/apache/incubator-trafodion/pull/471.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 #471


commit a2786b57d71e7876b204c0925047cf736b1ee44d
Author: Hans Zeller 
Date:   2016-05-10T01:47:19Z

TRAFODION-1983 Generator error 7000 with a salted table

commit a4caa9ac4afe331358a74b211784a08779ca298e
Author: Hans Zeller 
Date:   2016-05-10T01:49:18Z

TRAFODION-1710 setString() method and numerics with scale

The setString() method did not accept strings with digits after
the decimal point, like setString(1, "123.45").

commit 855759f387e7ab0fc677f6138ac5e580b2eeca39
Author: Hans Zeller 
Date:   2016-05-10T01:56:35Z

Misc cleanup items

Added a debugging method to print information for the list of all
Trafodion IPC connections in a process - that method can be called
from the debugger.

Removed unneeded code in preCodeGen - ValueIdSets for predicates imply
an AND, so no AND operators must be found in them.

Removed unnecessary flags in a makefile.




> Generator error 7000 (should never reach ...) with a salted table
> -
>
> Key: TRAFODION-1983
> URL: https://issues.apache.org/jira/browse/TRAFODION-1983
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.1-incubating
>
>
> Preparing such a query results in the following error:
> *** ERROR[7000] An internal error occurred in the code generator in file 
> ../generator/GenItemExpr.cpp at line nnn: 
> VEGRef_100((TRAFODION.MYSCHEMA.ORDERS.O_ORDERKEY = 100)) should never 
> reach ItemExpr::codeGen.
> To reproduce:
> CREATE TABLE ORDERS
>   (
> O_ORDERKEY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_CUSTKEYINT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_ORDERSTATUSCHAR(1) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_TOTALPRICE NUMERIC(12, 2) NO DEFAULT NOT NULL NOT
>   DROPPABLE SERIALIZED
>   , O_ORDERDATE  DATE NO DEFAULT NOT NULL NOT DROPPABLE 
> NOT
>   SERIALIZED
>   , O_ORDERPRIORITY  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_CLERK  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_SHIPPRIORITY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_COMMENTVARCHAR(79) CHARACTER SET ISO88591 
> COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , PRIMARY KEY (O_ORDERKEY ASC)
>   )
>   SALT USING 8 PARTITIONS
> ;
> cqd QUERY_CACHE '0';
> cqd CACHE_HISTOGRAMS reset;
> cqd HBASE_HASH2_PARTITIONING 'OFF';
> cqd HBASE_RANGE_PARTITIONING 'ON';
> prepare XX from select * from orders where o_orderkey = 100;



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

[jira] [Closed] (TRAFODION-1751) create table crash

2016-05-09 Thread liu ming (JIRA)


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

liu ming closed TRAFODION-1751.
---
   Resolution: Fixed
Fix Version/s: 2.0-incubating

fixed by others

> create table crash
> --
>
> Key: TRAFODION-1751
> URL: https://issues.apache.org/jira/browse/TRAFODION-1751
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> The following create table DDL will crash Trafodion instance.
> Tested in two different systems and can reproduce:
> in sqlci
> CREATE TABLE FactJCSales
> (
> ReportDateID   int  NOT NULL,
> FinanceDateID   int  NULL,
> ProvinceCenterID   int  NULL,
> CityCenterID   int  NULL,
> OrgKey   int  NULL,
> GameKey   int  NULL,
> DrawKey   int  NULL,
> TerminalKey   int  NULL,
> BranchID   int  NULL,
> ShopKey   int  NULL,
> LogonID   int  NULL,
> AccountID   int  NULL,
> TechSystemID   int  NULL,
> ChannelTypeCode   int  NULL,
> SaleLotteryCnt   int  NULL,
> SaleStakeCnt   int  NULL,
> SaleAmount   decimal (18, 4) NULL,
> SaleLotteryCntSettled   int  NULL,
> SaleStakeCntSettled   int  NULL,
> SaleAmountSettled   decimal (18, 4) NULL,
> CancelLotteryCnt   int  NULL,
> CancelStakeCnt   int  NULL,
> CancelAmount   decimal (18, 4) NULL,
> ProvCancelLotteryCnt   int  NULL,
> ProvCancelStakeCnt   int  NULL,
> ProvCancelAmount   decimal (18, 4) NULL,
> BranchCancelLotteryCnt   int  NULL,
> BranchCancelStakeCnt   int  NULL,
> BranchCancelAmount   decimal (18, 4) NULL
> )
>   store by (ReprotDateID)
>   SALT USING 80 PARTITIONS
>   HBASE_OPTIONS
>   (
> DATA_BLOCK_ENCODING = 'FAST_DIFF',
> COMPRESSION = 'SNAPPY',
> MEMSTORE_FLUSH_SIZE = '1073741824'
>   )
> ;
> *** EXECUTOR ASSERTION FAILURE
> *** Time: Mon Jan 11 08:57:50 2016
> *** Process: 6860
> *** File: ../common/Collections.cpp
> *** Line: 874
> *** Message: List index exceeds # of entries
> Aborted



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

[jira] [Commented] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

2016-05-09 Thread Gonzalo E Correa (JIRA)


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

Gonzalo E Correa commented on TRAFODION-1980:
-

There are two issues contributing to this behavior.

1. Analysis indicates that the 'shell' initialization logic is setting the 
state of physical node object to 'StateUp'. 

2. The method used to determine the physical state of a node is the use of an 
environment variable, i.e., NODE_LIST, which contains a list of host names 
which make up the cluster. This list is used to execute an 'ssh  
hostname' command across all the nodes. The hostnames returned are the nodes 
that are in an 'UP' state. However, if NODE_LIST does not contain a name, the 
state of the physical node object is not updated due to an early termination of 
the logic loop that sets the operational state of the physical node.

This causes subsequent request processing to honor the 'UP' request attempting 
to process it on a non-existent node, and it hangs.

Changing the initialization logic of physical node objects to a 'StateDown' 
appears to fix the behavior.

> Node up command (sqshell), when targeting a non-existing node, hangs.
> -
>
> Key: TRAFODION-1980
> URL: https://issues.apache.org/jira/browse/TRAFODION-1980
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.1-incubating
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.1-incubating
>
>
> When testing JIRA TRAFODION-1885 and targeting a node that does not exist and 
> is not set in the TRAF_EXCLUDE_LIST environment variable. The 'up' command 
> attempts to process and hangs. It should be returning an error indicating 
> that the node is not available.



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

[jira] [Assigned] (TRAFODION-1982) Server Packaging should be single tar file

2016-05-09 Thread Steve Varnau (JIRA)


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

Steve Varnau reassigned TRAFODION-1982:
---

Assignee: Steve Varnau

> Server Packaging should be single tar file
> --
>
> Key: TRAFODION-1982
> URL: https://issues.apache.org/jira/browse/TRAFODION-1982
> Project: Apache Trafodion
>  Issue Type: Bug
>Affects Versions: 2.0-incubating
>Reporter: Steve Varnau
>Assignee: Steve Varnau
>
> For historical reasons, server packaging is a tar of 3 tar files (server, 
> dcs, rest).  All of the contents should be in a single tar file.
> This also affects how the LICENSE files are assembled, since they treat this 
> as three separate distribution packages.
> This also affects installer since it expects either three tar files or a 
> tar-of-tars.



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

[jira] [Commented] (TRAFODION-1984) Installer packaging is not included in main package build target

2016-05-09 Thread Steve Varnau (JIRA)


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

Steve Varnau commented on TRAFODION-1984:
-

package name should also conform to artifact naming practice: 
apache-trafodion-installer--bin.tar.gz

> Installer packaging is not included in main package build target
> 
>
> Key: TRAFODION-1984
> URL: https://issues.apache.org/jira/browse/TRAFODION-1984
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: Build Infrastructure
>Affects Versions: 2.0-incubating
>Reporter: Steve Varnau
>Assignee: Steve Varnau
>
> installer packaging is a separate build for some reason



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

[jira] [Commented] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

2016-05-09 Thread Hans Zeller (JIRA)


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

Hans Zeller commented on TRAFODION-1983:


The issue is that we need to replace the VEG expression in the key predicate 
when we want to compute the number of active partitions at compile time. This 
is done with compile-time expression evaluation, which does not allow VEG 
expressions.

> Generator error 7000 (should never reach ...) with a salted table
> -
>
> Key: TRAFODION-1983
> URL: https://issues.apache.org/jira/browse/TRAFODION-1983
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.1-incubating
>
>
> Preparing such a query results in the following error:
> *** ERROR[7000] An internal error occurred in the code generator in file 
> ../generator/GenItemExpr.cpp at line nnn: 
> VEGRef_100((TRAFODION.MYSCHEMA.ORDERS.O_ORDERKEY = 100)) should never 
> reach ItemExpr::codeGen.
> To reproduce:
> CREATE TABLE ORDERS
>   (
> O_ORDERKEY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_CUSTKEYINT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_ORDERSTATUSCHAR(1) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_TOTALPRICE NUMERIC(12, 2) NO DEFAULT NOT NULL NOT
>   DROPPABLE SERIALIZED
>   , O_ORDERDATE  DATE NO DEFAULT NOT NULL NOT DROPPABLE 
> NOT
>   SERIALIZED
>   , O_ORDERPRIORITY  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_CLERK  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_SHIPPRIORITY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_COMMENTVARCHAR(79) CHARACTER SET ISO88591 
> COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , PRIMARY KEY (O_ORDERKEY ASC)
>   )
>   SALT USING 8 PARTITIONS
> ;
> cqd QUERY_CACHE '0';
> cqd CACHE_HISTOGRAMS reset;
> cqd HBASE_HASH2_PARTITIONING 'OFF';
> cqd HBASE_RANGE_PARTITIONING 'ON';
> prepare XX from select * from orders where o_orderkey = 100;



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

[jira] [Commented] (TRAFODION-1982) Server Packaging should be single tar file

2016-05-09 Thread Steve Varnau (JIRA)


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

Steve Varnau commented on TRAFODION-1982:
-

packaging file should also conform to apache naming practice  
"apache-trafodion-server--bin.tar.gz"
In this case, release = 2.0.0-incubating

> Server Packaging should be single tar file
> --
>
> Key: TRAFODION-1982
> URL: https://issues.apache.org/jira/browse/TRAFODION-1982
> Project: Apache Trafodion
>  Issue Type: Bug
>Affects Versions: 2.0-incubating
>Reporter: Steve Varnau
>
> For historical reasons, server packaging is a tar of 3 tar files (server, 
> dcs, rest).  All of the contents should be in a single tar file.
> This also affects how the LICENSE files are assembled, since they treat this 
> as three separate distribution packages.
> This also affects installer since it expects either three tar files or a 
> tar-of-tars.



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

[jira] [Created] (TRAFODION-1985) Server Packaging does not contain expected build-version.txt file

2016-05-09 Thread Steve Varnau (JIRA)

Steve Varnau created TRAFODION-1985:
---

 Summary: Server Packaging does not contain expected 
build-version.txt file
 Key: TRAFODION-1985
 URL: https://issues.apache.org/jira/browse/TRAFODION-1985
 Project: Apache Trafodion
  Issue Type: Bug
  Components: Build Infrastructure, installer
Affects Versions: 2.0-incubating
Reporter: Steve Varnau
Assignee: Steve Varnau


Installer depends on file (build-version.txt) that is generated by jenkins 
packaging steps. Either installer should not expect it, or the regular build 
process should include.

We should not depend on outside (jenkins) packaging steps.



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

[jira] [Created] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

2016-05-09 Thread Hans Zeller (JIRA)

Hans Zeller created TRAFODION-1983:
--

 Summary: Generator error 7000 (should never reach ...) with a 
salted table
 Key: TRAFODION-1983
 URL: https://issues.apache.org/jira/browse/TRAFODION-1983
 Project: Apache Trafodion
  Issue Type: Bug
  Components: sql-cmp
Affects Versions: 2.0-incubating
Reporter: Hans Zeller
 Fix For: 2.1-incubating


Preparing such a query results in the following error:

*** ERROR[7000] An internal error occurred in the code generator in file 
../generator/GenItemExpr.cpp at line nnn: 
VEGRef_100((TRAFODION.MYSCHEMA.ORDERS.O_ORDERKEY = 100)) should never reach 
ItemExpr::codeGen.


To reproduce:

CREATE TABLE ORDERS
  (
O_ORDERKEY   INT NO DEFAULT NOT NULL NOT DROPPABLE
  SERIALIZED
  , O_CUSTKEYINT NO DEFAULT NOT NULL NOT DROPPABLE
  SERIALIZED
  , O_ORDERSTATUSCHAR(1) CHARACTER SET ISO88591 COLLATE
  DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , O_TOTALPRICE NUMERIC(12, 2) NO DEFAULT NOT NULL NOT
  DROPPABLE SERIALIZED
  , O_ORDERDATE  DATE NO DEFAULT NOT NULL NOT DROPPABLE NOT
  SERIALIZED
  , O_ORDERPRIORITY  CHAR(15) CHARACTER SET ISO88591 COLLATE
  DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , O_CLERK  CHAR(15) CHARACTER SET ISO88591 COLLATE
  DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , O_SHIPPRIORITY   INT NO DEFAULT NOT NULL NOT DROPPABLE
  SERIALIZED
  , O_COMMENTVARCHAR(79) CHARACTER SET ISO88591 COLLATE
  DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
  , PRIMARY KEY (O_ORDERKEY ASC)
  )
  SALT USING 8 PARTITIONS
;

cqd QUERY_CACHE '0';
cqd CACHE_HISTOGRAMS reset;
cqd HBASE_HASH2_PARTITIONING 'OFF';
cqd HBASE_RANGE_PARTITIONING 'ON';

prepare XX from select * from orders where o_orderkey = 100;




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

[jira] [Work started] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

2016-05-09 Thread Hans Zeller (JIRA)


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

Work on TRAFODION-1983 started by Hans Zeller.
--
> Generator error 7000 (should never reach ...) with a salted table
> -
>
> Key: TRAFODION-1983
> URL: https://issues.apache.org/jira/browse/TRAFODION-1983
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.1-incubating
>
>
> Preparing such a query results in the following error:
> *** ERROR[7000] An internal error occurred in the code generator in file 
> ../generator/GenItemExpr.cpp at line nnn: 
> VEGRef_100((TRAFODION.MYSCHEMA.ORDERS.O_ORDERKEY = 100)) should never 
> reach ItemExpr::codeGen.
> To reproduce:
> CREATE TABLE ORDERS
>   (
> O_ORDERKEY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_CUSTKEYINT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_ORDERSTATUSCHAR(1) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_TOTALPRICE NUMERIC(12, 2) NO DEFAULT NOT NULL NOT
>   DROPPABLE SERIALIZED
>   , O_ORDERDATE  DATE NO DEFAULT NOT NULL NOT DROPPABLE 
> NOT
>   SERIALIZED
>   , O_ORDERPRIORITY  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_CLERK  CHAR(15) CHARACTER SET ISO88591 COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , O_SHIPPRIORITY   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , O_COMMENTVARCHAR(79) CHARACTER SET ISO88591 
> COLLATE
>   DEFAULT NO DEFAULT NOT NULL NOT DROPPABLE SERIALIZED
>   , PRIMARY KEY (O_ORDERKEY ASC)
>   )
>   SALT USING 8 PARTITIONS
> ;
> cqd QUERY_CACHE '0';
> cqd CACHE_HISTOGRAMS reset;
> cqd HBASE_HASH2_PARTITIONING 'OFF';
> cqd HBASE_RANGE_PARTITIONING 'ON';
> prepare XX from select * from orders where o_orderkey = 100;



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

[jira] [Created] (TRAFODION-1982) Server Packaging should be single tar file

2016-05-09 Thread Steve Varnau (JIRA)

Steve Varnau created TRAFODION-1982:
---

 Summary: Server Packaging should be single tar file
 Key: TRAFODION-1982
 URL: https://issues.apache.org/jira/browse/TRAFODION-1982
 Project: Apache Trafodion
  Issue Type: Bug
Affects Versions: 2.0-incubating
Reporter: Steve Varnau


For historical reasons, server packaging is a tar of 3 tar files (server, dcs, 
rest).  All of the contents should be in a single tar file.

This also affects how the LICENSE files are assembled, since they treat this as 
three separate distribution packages.

This also affects installer since it expects either three tar files or a 
tar-of-tars.



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

[jira] [Work started] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

2016-05-09 Thread Gonzalo E Correa (JIRA)


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

Work on TRAFODION-1980 started by Gonzalo E Correa.
---
> Node up command (sqshell), when targeting a non-existing node, hangs.
> -
>
> Key: TRAFODION-1980
> URL: https://issues.apache.org/jira/browse/TRAFODION-1980
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.1-incubating
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.1-incubating
>
>
> When testing JIRA TRAFODION-1885 and targeting a node that does not exist and 
> is not set in the TRAF_EXCLUDE_LIST environment variable. The 'up' command 
> attempts to process and hangs. It should be returning an error indicating 
> that the node is not available.



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

[jira] [Updated] (TRAFODION-1958) sqps and sqcheck display wrong information after node reintegrated

2016-05-09 Thread Suresh Subbiah (JIRA)


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

Suresh Subbiah updated TRAFODION-1958:
--
Assignee: Gonzalo E Correa

> sqps and sqcheck display wrong information after node reintegrated
> --
>
> Key: TRAFODION-1958
> URL: https://issues.apache.org/jira/browse/TRAFODION-1958
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.0-incubating
> Environment: all
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
>  Labels: CI, test
> Fix For: 2.0-incubating
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Looks like after a node failure/reintegration, we see this confusing behavior:
>  
> Processes with a ‘named’ parent process ‘may’ have incorrect info. When I did 
> an sqps on ctsha-2, see these processes on nid 3 without the program file 
> name (running sqps on nid 2, 3 or 4 gives the correct program name, which is 
> ‘tdm_arkcmp’):
> [$Z0019TI] 003,00012563 001 GEN ES--A-- $Z030A8Y $Z0316UD 
> [$Z0019TI] 003,00033477 001 GEN ES--A-- $Z030SBH $Z03171T 
> [$Z0019TI] 003,00033776 001 GEN ES--A-- $Z030SK1 $Z030SBH 
>  
> Local monitor has correct info about processes on its own node



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

[jira] [Updated] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

2016-05-09 Thread Suresh Subbiah (JIRA)


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

Suresh Subbiah updated TRAFODION-1980:
--
Assignee: Gonzalo E Correa

> Node up command (sqshell), when targeting a non-existing node, hangs.
> -
>
> Key: TRAFODION-1980
> URL: https://issues.apache.org/jira/browse/TRAFODION-1980
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.1-incubating
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.1-incubating
>
>
> When testing JIRA TRAFODION-1885 and targeting a node that does not exist and 
> is not set in the TRAF_EXCLUDE_LIST environment variable. The 'up' command 
> attempts to process and hangs. It should be returning an error indicating 
> that the node is not available.



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

[jira] [Updated] (TRAFODION-1710) TMUDF: setString method does not accept non-integers for NUMERIC type

2016-05-09 Thread Hans Zeller (JIRA)


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

Hans Zeller updated TRAFODION-1710:
---
Fix Version/s: (was: 2.0-incubating)
   2.1-incubating

> TMUDF: setString method does not accept non-integers for NUMERIC type
> -
>
> Key: TRAFODION-1710
> URL: https://issues.apache.org/jira/browse/TRAFODION-1710
> Project: Apache Trafodion
>  Issue Type: Bug
>Affects Versions: any
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.1-incubating
>
>
> When calling the TupleInfo.setString() method to set a NUMERIC column from a 
> string, an exception is raised when the string contains a decimal point, like 
> 123.45.
> Internally, this method calls setLong(), which expects a scaled up value, 
> e.g. 123450. The code to do that scaling is missing. This affects both the 
> Java and the C++  interface for TMUDFs.



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

[jira] [Updated] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

2016-05-09 Thread Gonzalo E Correa (JIRA)


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

Gonzalo E Correa updated TRAFODION-1980:

Summary: Node up command (sqshell), when targeting a non-existing node, 
hangs.  (was: Node up command (sqshell), when done to a non-existing node, 
hangs.)

> Node up command (sqshell), when targeting a non-existing node, hangs.
> -
>
> Key: TRAFODION-1980
> URL: https://issues.apache.org/jira/browse/TRAFODION-1980
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.1-incubating
>Reporter: Gonzalo E Correa
> Fix For: 2.1-incubating
>
>
> When testing JIRA TRAFODION-1885 and targeting a node that does not exist and 
> is not set in the TRAF_EXCLUDE_LIST environment variable. The 'up' command 
> attempts to process and hangs. It should be returning an error indicating 
> that the node is not available.



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

[jira] [Commented] (TRAFODION-1978) Skip LOB columns for UPDATE STATS

[jira] [Created] (TRAFODION-1986) trafodion jdbc t4 api can't set schema

[jira] [Commented] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

[jira] [Closed] (TRAFODION-1751) create table crash

[jira] [Commented] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

[jira] [Assigned] (TRAFODION-1982) Server Packaging should be single tar file

[jira] [Commented] (TRAFODION-1984) Installer packaging is not included in main package build target

[jira] [Commented] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

[jira] [Commented] (TRAFODION-1982) Server Packaging should be single tar file

[jira] [Created] (TRAFODION-1985) Server Packaging does not contain expected build-version.txt file

[jira] [Created] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

[jira] [Work started] (TRAFODION-1983) Generator error 7000 (should never reach ...) with a salted table

[jira] [Created] (TRAFODION-1982) Server Packaging should be single tar file

[jira] [Work started] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

[jira] [Updated] (TRAFODION-1958) sqps and sqcheck display wrong information after node reintegrated

[jira] [Updated] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

[jira] [Updated] (TRAFODION-1710) TMUDF: setString method does not accept non-integers for NUMERIC type

[jira] [Updated] (TRAFODION-1980) Node up command (sqshell), when targeting a non-existing node, hangs.

18 matches

Site Navigation

Mail list logo

Footer information