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

[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)

[jira] [Work started] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column

[liu ming (JIRA)]

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

Work on TRAFODION-1858 started by liu ming.
---
> RI predicate generating string should not contain _SALT_ column
> ---
>
> Key: TRAFODION-1858
> URL: https://issues.apache.org/jira/browse/TRAFODION-1858
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> When table created with SALT, it cannot be used in a foreign key reference.
> To reproduce:
> >>CREATE TABLE a ( id int not null, PRIMARY KEY (id))SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>CREATE TABLE b ( id int not null, val int,
> +>  PRIMARY KEY (id),
> +>  CONSTRAINT FK FOREIGN KEY (val) REFERENCES a (id))
> +>SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>INSERT INTO a values(1);
> --- 1 row(s) inserted.
> >>INSERT INTO b values(1,1);
> *** ERROR[15001] A syntax error occurred at or before: 
> ("NEW@".VAL)=(TRAFODION.SEABASE.A."_SALT_",TRAFODION.SEABASE.A.ID);
>   ^ (43 characters from start of SQL 
> statement)
> *** ERROR[8822] The statement was not prepared.



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

[jira] [Commented] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1858:
-

in core/sql/optimizer/BindRI.cpp
RefConstraint::getPredicateText()
one should check the column name, if it is "_SALT_", ignore it.
I assume there are other 'hidden' column as well. Need to get a list of them.

> RI predicate generating string should not contain _SALT_ column
> ---
>
> Key: TRAFODION-1858
> URL: https://issues.apache.org/jira/browse/TRAFODION-1858
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> When table created with SALT, it cannot be used in a foreign key reference.
> To reproduce:
> >>CREATE TABLE a ( id int not null, PRIMARY KEY (id))SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>CREATE TABLE b ( id int not null, val int,
> +>  PRIMARY KEY (id),
> +>  CONSTRAINT FK FOREIGN KEY (val) REFERENCES a (id))
> +>SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>INSERT INTO a values(1);
> --- 1 row(s) inserted.
> >>INSERT INTO b values(1,1);
> *** ERROR[15001] A syntax error occurred at or before: 
> ("NEW@".VAL)=(TRAFODION.SEABASE.A."_SALT_",TRAFODION.SEABASE.A.ID);
>   ^ (43 characters from start of SQL 
> statement)
> *** ERROR[8822] The statement was not prepared.



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

[jira] [Assigned] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1858:
---

Assignee: liu ming

> RI predicate generating string should not contain _SALT_ column
> ---
>
> Key: TRAFODION-1858
> URL: https://issues.apache.org/jira/browse/TRAFODION-1858
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> When table created with SALT, it cannot be used in a foreign key reference.
> To reproduce:
> >>CREATE TABLE a ( id int not null, PRIMARY KEY (id))SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>CREATE TABLE b ( id int not null, val int,
> +>  PRIMARY KEY (id),
> +>  CONSTRAINT FK FOREIGN KEY (val) REFERENCES a (id))
> +>SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>INSERT INTO a values(1);
> --- 1 row(s) inserted.
> >>INSERT INTO b values(1,1);
> *** ERROR[15001] A syntax error occurred at or before: 
> ("NEW@".VAL)=(TRAFODION.SEABASE.A."_SALT_",TRAFODION.SEABASE.A.ID);
>   ^ (43 characters from start of SQL 
> statement)
> *** ERROR[8822] The statement was not prepared.



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

[jira] [Closed] (TRAFODION-1813) add commons-httpclient depenedency into dcs/pom.xml

[liu ming (JIRA)]

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

liu ming closed TRAFODION-1813.
---
Resolution: Not A Problem

not an issue. Close.

> add commons-httpclient depenedency into dcs/pom.xml
> ---
>
> Key: TRAFODION-1813
> URL: https://issues.apache.org/jira/browse/TRAFODION-1813
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
>
> Not sure why the dependency of httpclient is missing from pom.xml under dcs 
> folder, it doesn't affect build in most cases, but I cannot make a build on a 
> fresh machine, so suggest to explicit add this dependency.



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

[jira] [Assigned] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1834:
---

Assignee: liu ming

> ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in 
> sqconfig are fully qualified
> --
>
> Key: TRAFODION-1834
> URL: https://issues.apache.org/jira/browse/TRAFODION-1834
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.3-incubating
>Reporter: Atanu Mishra
>Assignee: liu ming
>
> Paraphrasing Hans, who looked into this briefly: 
> Looking at the code, I can see that we remove anything from the first dot in 
> the node name of the region. Then we search for the unqualified node name in 
> the list of node names of the Trafodion cluster.
> Both of these clusters use FQDNs in their configuration, though, therefore we 
> won't find the node names.
> To Reproduce:
> Do an EXPLAIN of a parallel query with and without TRAF_ALLOW_ESP_COLOCATION 
> set, and the node map will not show a co-located plan when the CQD is on - if 
> the system uses FQDNs in its sqconfig file.



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

[jira] [Commented] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1834:
-

The issue is slightly different. The FQDN is not a problem.

The binder will build the initial node_map for a given table, at that time, the 
API invoked is called createNodeMapForHbase(), in that function, it will 
truncate the FQDN into hostname. And the NAClusterInfo class which collecting 
the hostname to nodeId mapping will also do the truncation. So it is a match.

But there is a new problem that this jira will fix:
In a system, there is a cluster with 10 nodes, HBase RS installed on 8 of them. 
Table bltest have 100M rows, 250G in one-replica size, split into 100 regions, 
evenly spread over 8 nodes.

do a very simple test: 
select [last 1]* from bltest;
Without this CQD set, it launched 10 ESPs over 10 nodes, and the ESP node_map 
printed as:
 
esp_2_node_map . (\NSK:-1:-1:-1:-1:-1:-1:-1:-1:-1:-1)
 
which means randomly locate each ESP
With this CQD, each time, the node_map is different, such as:
 
esp_2_node_map . (\NSK:0:0:0:0:0:0:0:0:0:0)
esp_2_node_map . (\NSK:7:7:7:7:7:7:7:7:7:7)
 
you can notice, the 10 ESP will be put into same node when CQD is ‘on’, and the 
node number is random. 
 
This bug is in optimizer’s NodeMap::getPopularNodeNumber() function, it tries 
to find out a most popular node. In above case, 10 ESPs try to read 100 
regions, so for the first ESP, it needs to read 10 regions, 0~9, but region 0 
and region 1 may be in different RS node, so this function is trying to find a 
RS which serves the most regions from Region 0 to Region 9, and locate first 
ESP there. 
But this function use an uninitialized array to do the job. It malloc a new 
buffer and use as counter array, but GCC is not always clear the newly alloc 
buffer, so you never know what init value in that array, so if node[0] init 
with a very big number, it will always win, and we saw:
esp_2_node_map . (\NSK:0:0:0:0:0:0:0:0:0:0)

a fix is to init the array.

And in this change, we remove the bias in getPopularNodeNumber() to lowest node 
ID, but make it random.

> ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in 
> sqconfig are fully qualified
> --
>
> Key: TRAFODION-1834
> URL: https://issues.apache.org/jira/browse/TRAFODION-1834
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.3-incubating
>Reporter: Atanu Mishra
>Assignee: liu ming
>
> Paraphrasing Hans, who looked into this briefly: 
> Looking at the code, I can see that we remove anything from the first dot in 
> the node name of the region. Then we search for the unqualified node name in 
> the list of node names of the Trafodion cluster.
> Both of these clusters use FQDNs in their configuration, though, therefore we 
> won't find the node names.
> To Reproduce:
> Do an EXPLAIN of a parallel query with and without TRAF_ALLOW_ESP_COLOCATION 
> set, and the node map will not show a co-located plan when the CQD is on - if 
> the system uses FQDNs in its sqconfig file.



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

[jira] [Commented] (TRAFODION-1841) DROP TABLE just after CREATE TABLE fails

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1841:
-

seems not reproducible, I tested on my two dev system with latest code, not see 
same issue. Recommend to build from scratch and run install_local_hadoop from 
scratch. 

> DROP TABLE just after CREATE TABLE fails
> 
>
> Key: TRAFODION-1841
> URL: https://issues.apache.org/jira/browse/TRAFODION-1841
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
> Environment: This happened on a workstation. Don't know if it happens 
> everywhere.
>Reporter: David Wayne Birdsall
>
> If one creates a table in sqlci and then drops it, the drop fails. An example:
> [birdsall@edev05 Traf1838]$ sqlci
> Apache Trafodion Conversational Interface 2.0.0
> Copyright (c) 2015 Apache Software Foundation
> >>create table t2 (a int);
> --- SQL operation complete.
> >>drop table t2;
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::deleteRow returned error HBASE_ACCESS_ERROR(-706). Cause: 
> java.io.IOException: Coprocessor result is null, retries exhausted
> org.apache.hadoop.hbase.client.transactional.TransactionalTable.delete(TransactionalTable.java:300)
> org.apache.hadoop.hbase.client.transactional.RMInterface.delete(RMInterface.java:325)
> org.trafodion.sql.HTableClient.deleteRow(HTableClient.java:1377)
> org.trafodion.sql.HBaseClient.deleteRow(HBaseClient.java:1680)
> .
> *** ERROR[8839] Transaction was aborted.
> (The failure then repeats several times, possibly because of a retry loop in 
> the code.)
> I am wondering if this is related at all to JIRA TRAFODION-1729.



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

[jira] [Created] (TRAFODION-1861) support Trafodion running on CentOS 7

[liu ming (JIRA)]

liu ming created TRAFODION-1861:
---

 Summary: support Trafodion running on CentOS 7
 Key: TRAFODION-1861
 URL: https://issues.apache.org/jira/browse/TRAFODION-1861
 Project: Apache Trafodion
  Issue Type: Umbrella
Reporter: liu ming






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

[jira] [Resolved] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1854.
-
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Reopened] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

liu ming reopened TRAFODION-1854:
-

The original fix not correct, problem still there, need rework

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Work started] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

Work on TRAFODION-1854 started by liu ming.
---
> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Resolved] (TRAFODION-1865) uninitialized buffer cause Monitor abort in CentOS 7

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1865.
-
   Resolution: Duplicate
Fix Version/s: 2.0-incubating

jira TRAFODION-1868 takes care of this issue instead.

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Commented] (TRAFODION-1865) uninitialized buffer cause Monitor abort in CentOS 7

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1865:
-

The root cause is incompatibility of glibc from CentOS 6 to CentOS 7. 
It has no relationship with uninitialized buffer.
The right solution is to build trafodion binary using gcc 4.8 under centOS 7 to 
run it on CentOS 7.
So close this jira now.

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Commented] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1869:
-

improper link order of ms.o and mpitmsg.o to build libsbms
CentOS 7.2 dynamic linker will invoke constructor in the order of the link 
order. 
Will fix it soon.

> 'initialized trafodion' failed on CentOS 7.2
> 
>
> Key: TRAFODION-1869
> URL: https://issues.apache.org/jira/browse/TRAFODION-1869
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> On CentOS 7.2, install Trafodion then run 'initialize trafodion'
> >>initialize trafodion;
> *** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating 
> with server process $Z000I2H:52.
> *** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - 
> Operating system error 201.
> *** ERROR[2002] Internal error: cannot create compiler.
> *** ERROR[2005] Internal error: from compilation, no errors in diagnostics 
> yet for statement: control query shape hold;
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> related core is from tdm_arkcmp
> Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H 
> 192.168.0.10:56579 4 0'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x in ?? ()
> Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 
> trafodion-2.0.1-devel.x86_64
> (gdb) bt
> #0  0x in ?? ()
> #1  0x7f44a8552fc6 in SB_Thread::Sthr::time () at 
> /home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115
> #2  0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4,
> pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, 
> pv_int=false, pv_ts=false) at fsi.cpp:1301
> #3  0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0,
> pv_timeout=6, pp_segid=0x0) at fs.cpp:563
> #4  0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, 
> timeout=6, eventConsumed=, ipcAwaitiox=0x0)
> at ../common/IpcGuardian.cpp:2692
> #5  0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster 
> (this=0x1603020) at ../common/IpcGuardian.cpp:3603
> #6  0x00406366 in main ()
> (gdb)



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

[jira] [Created] (TRAFODION-1881) Follow up TRAFODION-1858 , need a better fix

[liu ming (JIRA)]

liu ming created TRAFODION-1881:
---

 Summary: Follow up TRAFODION-1858 , need a better fix
 Key: TRAFODION-1881
 URL: https://issues.apache.org/jira/browse/TRAFODION-1881
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming


TRAFODION-1858 is now fixed using a temp method. A better and complete solution 
is required. 
But to solve it entirely, it requires a more throughout refactor of many 
related parts of code.
It is a real customer blocking issue, so we fix it with the temp solution and 
using this JIRA to follow up. 
The solution in TRAFODION-1858 is to add a new method to check the string name 
of a given column to tell if it is SALT column, or DIVSION column. The checking 
method is hardcoding the naming conversion, which may change and break the 
function.
However, to use NAColumn's built-in helper checking methods, it needs the SQL 
compiler to generate correct constraint info from begining and change all the 
intermediate objects along the path. It may also need to change the METATABLE 
which contains information about constraints.
So we use this JIRA to track, and need a longer time to find a good solution to 
solve TRAFODION-1858.



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

[jira] [Commented] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1858:
-

TRAFODION-1880 is created for same issue and replace this JIRA.
This JIRA will be closed with a temp ,simple solution.
TRAFODION-1880 will track the effort to find a complete total solution to this 
kind of issue.

> RI predicate generating string should not contain _SALT_ column
> ---
>
> Key: TRAFODION-1858
> URL: https://issues.apache.org/jira/browse/TRAFODION-1858
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> When table created with SALT, it cannot be used in a foreign key reference.
> To reproduce:
> >>CREATE TABLE a ( id int not null, PRIMARY KEY (id))SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>CREATE TABLE b ( id int not null, val int,
> +>  PRIMARY KEY (id),
> +>  CONSTRAINT FK FOREIGN KEY (val) REFERENCES a (id))
> +>SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>INSERT INTO a values(1);
> --- 1 row(s) inserted.
> >>INSERT INTO b values(1,1);
> *** ERROR[15001] A syntax error occurred at or before: 
> ("NEW@".VAL)=(TRAFODION.SEABASE.A."_SALT_",TRAFODION.SEABASE.A.ID);
>   ^ (43 characters from start of SQL 
> statement)
> *** ERROR[8822] The statement was not prepared.



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

[jira] [Work started] (TRAFODION-1890) disable SSCC entirely in current Trafodion

[liu ming (JIRA)]

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

Work on TRAFODION-1890 started by liu ming.
---
> disable SSCC entirely in current Trafodion
> --
>
> Key: TRAFODION-1890
> URL: https://issues.apache.org/jira/browse/TRAFODION-1890
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
>
> I have difficulties to start HBase using 'install_local_hadoop' each time I 
> have a new workspace. 
> Most of the time, I simply remove the sscc coprocessor from hbase-site.xml 
> and hbase can start well.
> Since SSCC has not been maintained for a long time, and need more effort to 
> test it again. So I think we should disable it totally and remove it from 
> hbase-site.xml



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

[jira] [Created] (TRAFODION-1890) disable SSCC entirely in current Trafodion

[liu ming (JIRA)]

liu ming created TRAFODION-1890:
---

 Summary: disable SSCC entirely in current Trafodion
 Key: TRAFODION-1890
 URL: https://issues.apache.org/jira/browse/TRAFODION-1890
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming
Assignee: liu ming
Priority: Minor


I have difficulties to start HBase using 'install_local_hadoop' each time I 
have a new workspace. 
Most of the time, I simply remove the sscc coprocessor from hbase-site.xml and 
hbase can start well.
Since SSCC has not been maintained for a long time, and need more effort to 
test it again. So I think we should disable it totally and remove it from 
hbase-site.xml




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

[jira] [Assigned] (TRAFODION-1868) Compatibility with gcc 4.8

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1868:
---

Assignee: 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: 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-1868) Compatibility with gcc 4.8

[liu ming (JIRA)]

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

Work on TRAFODION-1868 started by 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: 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] [Resolved] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1854.
-
Resolution: Fixed

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Commented] (TRAFODION-1920) suppress SQL error during HIVE_SCAN when encounter invalid value, assign null to the invalid value

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1920:
-

The converting is done by applying convertExpr() inside 
ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow().
We need to modify the Pcode runtime behavior by converting an invalid value 
into null.
We also need to modify the slow path of expression evaluation to do same thing, 
but priority is lower.

> suppress SQL error during HIVE_SCAN when encounter invalid value, assign null 
> to the invalid value
> --
>
> Key: TRAFODION-1920
> URL: https://issues.apache.org/jira/browse/TRAFODION-1920
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>Assignee: liu ming
>




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

[jira] [Work started] (TRAFODION-1920) suppress SQL error during HIVE_SCAN when encounter invalid value, assign null to the invalid value

[liu ming (JIRA)]

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

Work on TRAFODION-1920 started by liu ming.
---
> suppress SQL error during HIVE_SCAN when encounter invalid value, assign null 
> to the invalid value
> --
>
> Key: TRAFODION-1920
> URL: https://issues.apache.org/jira/browse/TRAFODION-1920
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>Assignee: liu ming
>




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

[jira] [Created] (TRAFODION-1901) allow more flexible column-definition in create table ddl

[liu ming (JIRA)]

liu ming created TRAFODION-1901:
---

 Summary: allow more flexible column-definition in create table ddl
 Key: TRAFODION-1901
 URL: https://issues.apache.org/jira/browse/TRAFODION-1901
 Project: Apache Trafodion
  Issue Type: Improvement
Reporter: liu ming


Current Trafodion DDL syntax for CREATE TABLE is very strict to ANSI standard 
about column-definition.
column-definition is:

column data-type
[DEFAULT default | NO DEFAULT]
[[CONSTRAINT constraint-name] column-constraint]

So constraint like 'NOT NULL' must follow the DEFAULT descriptor. In many other 
databases, this is allowed. So if Trafodion make this more flexible, it will 
help database migration.

Here is a test case:

CREATE TABLE TABLETEST1
(MARK_ID SMALLINTNOT NULL,
  BEGIN_TIME  DATENOT NULL  DEFAULT date'2008-01-01',
  END_TIMEDATENOT NULL  DEFAULT date'2018-01-01',
  ACTIVE_FLAG SMALLINT,
  MARK_NAME   VARCHAR(20),
  DESC_TXTVARCHAR(80),
  primary key(MARK_ID, BEGIN_TIME, END_TIME)
);
*** ERROR[15001] A syntax error occurred at or before:
CREATE TABLE TABLETEST  (MARK_ID SMALLINTNO
T NULL,   BEGIN_TIME  DATENOT NULL  DEFAULT date'2008-01-01',   END
  ^ (134 characters from 
start of SQL statement)

*** ERROR[8822] The statement was not prepared.

Trafodion support of above DDL will greatly simplify the database migration 
from other databases into Trafodion.





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

[jira] [Resolved] (TRAFODION-1890) disable SSCC entirely in current Trafodion

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1890.
-
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> disable SSCC entirely in current Trafodion
> --
>
> Key: TRAFODION-1890
> URL: https://issues.apache.org/jira/browse/TRAFODION-1890
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
> Fix For: 2.0-incubating
>
>
> I have difficulties to start HBase using 'install_local_hadoop' each time I 
> have a new workspace. 
> Most of the time, I simply remove the sscc coprocessor from hbase-site.xml 
> and hbase can start well.
> Since SSCC has not been maintained for a long time, and need more effort to 
> test it again. So I think we should disable it totally and remove it from 
> hbase-site.xml



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

[jira] [Closed] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column

[liu ming (JIRA)]

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

liu ming closed TRAFODION-1858.
---

There is TRAFODION-1880 which continue on this issue. This is a temp solution.

> RI predicate generating string should not contain _SALT_ column
> ---
>
> Key: TRAFODION-1858
> URL: https://issues.apache.org/jira/browse/TRAFODION-1858
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> When table created with SALT, it cannot be used in a foreign key reference.
> To reproduce:
> >>CREATE TABLE a ( id int not null, PRIMARY KEY (id))SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>CREATE TABLE b ( id int not null, val int,
> +>  PRIMARY KEY (id),
> +>  CONSTRAINT FK FOREIGN KEY (val) REFERENCES a (id))
> +>SALT USING 9 PARTITIONS;
> --- SQL operation complete.
> >>INSERT INTO a values(1);
> --- 1 row(s) inserted.
> >>INSERT INTO b values(1,1);
> *** ERROR[15001] A syntax error occurred at or before: 
> ("NEW@".VAL)=(TRAFODION.SEABASE.A."_SALT_",TRAFODION.SEABASE.A.ID);
>   ^ (43 characters from start of SQL 
> statement)
> *** ERROR[8822] The statement was not prepared.



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

[jira] [Work started] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified

[liu ming (JIRA)]

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

Work on TRAFODION-1834 started by liu ming.
---
> ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in 
> sqconfig are fully qualified
> --
>
> Key: TRAFODION-1834
> URL: https://issues.apache.org/jira/browse/TRAFODION-1834
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.3-incubating
>Reporter: Atanu Mishra
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> Paraphrasing Hans, who looked into this briefly: 
> Looking at the code, I can see that we remove anything from the first dot in 
> the node name of the region. Then we search for the unqualified node name in 
> the list of node names of the Trafodion cluster.
> Both of these clusters use FQDNs in their configuration, though, therefore we 
> won't find the node names.
> To Reproduce:
> Do an EXPLAIN of a parallel query with and without TRAF_ALLOW_ESP_COLOCATION 
> set, and the node map will not show a co-located plan when the CQD is on - if 
> the system uses FQDNs in its sqconfig file.



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

[jira] [Work stopped] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified

[liu ming (JIRA)]

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

Work on TRAFODION-1834 stopped by liu ming.
---
> ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in 
> sqconfig are fully qualified
> --
>
> Key: TRAFODION-1834
> URL: https://issues.apache.org/jira/browse/TRAFODION-1834
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.3-incubating
>Reporter: Atanu Mishra
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> Paraphrasing Hans, who looked into this briefly: 
> Looking at the code, I can see that we remove anything from the first dot in 
> the node name of the region. Then we search for the unqualified node name in 
> the list of node names of the Trafodion cluster.
> Both of these clusters use FQDNs in their configuration, though, therefore we 
> won't find the node names.
> To Reproduce:
> Do an EXPLAIN of a parallel query with and without TRAF_ALLOW_ESP_COLOCATION 
> set, and the node map will not show a co-located plan when the CQD is on - if 
> the system uses FQDNs in its sqconfig file.



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

[jira] [Resolved] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1834.
-
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in 
> sqconfig are fully qualified
> --
>
> Key: TRAFODION-1834
> URL: https://issues.apache.org/jira/browse/TRAFODION-1834
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 1.3-incubating
>Reporter: Atanu Mishra
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> Paraphrasing Hans, who looked into this briefly: 
> Looking at the code, I can see that we remove anything from the first dot in 
> the node name of the region. Then we search for the unqualified node name in 
> the list of node names of the Trafodion cluster.
> Both of these clusters use FQDNs in their configuration, though, therefore we 
> won't find the node names.
> To Reproduce:
> Do an EXPLAIN of a parallel query with and without TRAF_ALLOW_ESP_COLOCATION 
> set, and the node map will not show a co-located plan when the CQD is on - if 
> the system uses FQDNs in its sqconfig file.



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

[jira] [Updated] (TRAFODION-1878) Create a docker environment

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1878:

Assignee: Nitin Lamba

> Create a docker environment
> ---
>
> Key: TRAFODION-1878
> URL: https://issues.apache.org/jira/browse/TRAFODION-1878
> Project: Apache Trafodion
>  Issue Type: New Feature
>  Components: dev-environment
>Reporter: Nitin Lamba
>Assignee: Nitin Lamba
>
> Create a portable development environment using docker.



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

[jira] [Updated] (TRAFODION-1875) 'sqnodeipcrm' script failed to parse node name during sqstart

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1875:

Assignee: Eason Zhang

> 'sqnodeipcrm' script failed to parse node name during sqstart
> -
>
> Key: TRAFODION-1875
> URL: https://issues.apache.org/jira/browse/TRAFODION-1875
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> If there's 'dot' in trafodion directory name, the script 'sqnodeipcrm' will 
> fail to parse the correct node name during sqstart:
> /home/trafodion/trafodion-1.3.0/sql/scripts/sqnodeipcrm: line 28: let: 
> lv_virtual_node=0/tmp/monitor: division by 0 (error token is "/monitor")



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

[jira] [Created] (TRAFODION-1874) find a new way to check CLUSTER environment instead of checking pdsh

[liu ming (JIRA)]

liu ming created TRAFODION-1874:
---

 Summary: 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
Reporter: 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-1865) uninitialized buffer cause Monitor abort in CentOS 7

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1865:
-

the problem is not caused by 'uninitialized buffer, the title is not proper. 
Will continue to work on this.

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Work started] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

Work on TRAFODION-1854 started by liu ming.
---
> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Assigned] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1869:
---

Assignee: liu ming

> 'initialized trafodion' failed on CentOS 7.2
> 
>
> Key: TRAFODION-1869
> URL: https://issues.apache.org/jira/browse/TRAFODION-1869
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> On CentOS 7.2, install Trafodion then run 'initialize trafodion'
> >>initialize trafodion;
> *** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating 
> with server process $Z000I2H:52.
> *** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - 
> Operating system error 201.
> *** ERROR[2002] Internal error: cannot create compiler.
> *** ERROR[2005] Internal error: from compilation, no errors in diagnostics 
> yet for statement: control query shape hold;
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> related core is from tdm_arkcmp
> Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H 
> 192.168.0.10:56579 4 0'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x in ?? ()
> Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 
> trafodion-2.0.1-devel.x86_64
> (gdb) bt
> #0  0x in ?? ()
> #1  0x7f44a8552fc6 in SB_Thread::Sthr::time () at 
> /home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115
> #2  0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4,
> pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, 
> pv_int=false, pv_ts=false) at fsi.cpp:1301
> #3  0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0,
> pv_timeout=6, pp_segid=0x0) at fs.cpp:563
> #4  0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, 
> timeout=6, eventConsumed=, ipcAwaitiox=0x0)
> at ../common/IpcGuardian.cpp:2692
> #5  0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster 
> (this=0x1603020) at ../common/IpcGuardian.cpp:3603
> #6  0x00406366 in main ()
> (gdb)



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

[jira] [Work started] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2

[liu ming (JIRA)]

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

Work on TRAFODION-1869 started by liu ming.
---
> 'initialized trafodion' failed on CentOS 7.2
> 
>
> Key: TRAFODION-1869
> URL: https://issues.apache.org/jira/browse/TRAFODION-1869
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> On CentOS 7.2, install Trafodion then run 'initialize trafodion'
> >>initialize trafodion;
> *** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating 
> with server process $Z000I2H:52.
> *** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - 
> Operating system error 201.
> *** ERROR[2002] Internal error: cannot create compiler.
> *** ERROR[2005] Internal error: from compilation, no errors in diagnostics 
> yet for statement: control query shape hold;
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> related core is from tdm_arkcmp
> Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H 
> 192.168.0.10:56579 4 0'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x in ?? ()
> Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 
> trafodion-2.0.1-devel.x86_64
> (gdb) bt
> #0  0x in ?? ()
> #1  0x7f44a8552fc6 in SB_Thread::Sthr::time () at 
> /home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115
> #2  0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4,
> pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, 
> pv_int=false, pv_ts=false) at fsi.cpp:1301
> #3  0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0,
> pv_timeout=6, pp_segid=0x0) at fs.cpp:563
> #4  0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, 
> timeout=6, eventConsumed=, ipcAwaitiox=0x0)
> at ../common/IpcGuardian.cpp:2692
> #5  0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster 
> (this=0x1603020) at ../common/IpcGuardian.cpp:3603
> #6  0x00406366 in main ()
> (gdb)



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

[jira] [Commented] (TRAFODION-1868) Compatibility with gcc 4.8

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1868:
-

there are multiple issues to build using gcc 4.8.
1. Werror
  gcc 4.8 is more strict than gcc 4.4. There are several programming issues 
that not reported as warning by 4.4
  - declare and init a var , but never use it anymore
  - assign 0 to a pointer var
  - etc.
2. syntax checking
  gcc 4.8 will report error for some code like
  for ( int idx = 0; idx < 100; idx++)
  {
ANewClass idx = new ANewClass();
...
  need to fix these issues. 
3. boost conflict with c++11
4. must use -Xlinker --copy-dt-needed-entries, otherwise linker will not find 
all required so automatically.

These are some issues I met, issues related to item 1 are too many. I temply 
remove -Werror to overcome it. and make a build. But we need to fix all issues 
related to item 1.

There are so many changes to many src code. So I suggest to do this 
increamentally. It is easier to test, and easier for others to do code review.


> 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
>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] [Updated] (TRAFODION-1861) support Trafodion running on CentOS 7

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1861:

Assignee: Eason Zhang

> support Trafodion running on CentOS 7
> -
>
> Key: TRAFODION-1861
> URL: https://issues.apache.org/jira/browse/TRAFODION-1861
> Project: Apache Trafodion
>  Issue Type: Umbrella
>Reporter: liu ming
>Assignee: Eason Zhang
>




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

[jira] [Assigned] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1854:
---

Assignee: liu ming

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Commented] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1854:
-

Monitor's CClusterConfig class treat all character as lower case when reading 
the cluster configuration file.
Monitor will not use hostname in normal operation, so convert the hostname into 
lowercase in shell.cxx will solve the issue.

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Created] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2

[liu ming (JIRA)]

liu ming created TRAFODION-1869:
---

 Summary: 'initialized trafodion' failed on CentOS 7.2
 Key: TRAFODION-1869
 URL: https://issues.apache.org/jira/browse/TRAFODION-1869
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming


On CentOS 7.2, install Trafodion then run 'initialize trafodion'

>>initialize trafodion;

*** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating 
with server process $Z000I2H:52.

*** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - 
Operating system error 201.

*** ERROR[2002] Internal error: cannot create compiler.

*** ERROR[2005] Internal error: from compilation, no errors in diagnostics yet 
for statement: control query shape hold;

*** ERROR[8822] The statement was not prepared.

--- SQL operation failed with errors.


related core is from tdm_arkcmp
Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H 
192.168.0.10:56579 4 0'.
Program terminated with signal 11, Segmentation fault.
#0  0x in ?? ()
Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 
trafodion-2.0.1-devel.x86_64
(gdb) bt
#0  0x in ?? ()
#1  0x7f44a8552fc6 in SB_Thread::Sthr::time () at 
/home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115
#2  0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, 
ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4,
pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, 
pv_int=false, pv_ts=false) at fsi.cpp:1301
#3  0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, 
ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0,
pv_timeout=6, pp_segid=0x0) at fs.cpp:563
#4  0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, 
timeout=6, eventConsumed=, ipcAwaitiox=0x0)
at ../common/IpcGuardian.cpp:2692
#5  0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster 
(this=0x1603020) at ../common/IpcGuardian.cpp:3603
#6  0x00406366 in main ()
(gdb)




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

[jira] [Updated] (TRAFODION-1860) sqgen failed to execute on CentOS7 system.

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1860:

Assignee: Eason Zhang

> sqgen failed to execute on CentOS7 system.
> --
>
> Key: TRAFODION-1860
> URL: https://issues.apache.org/jira/browse/TRAFODION-1860
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> missing ctime.pl file on CentOS7.
> [trafodion@vmcentos7 ~]$ sqgen   
> Workstation environment - Not a clustered environment
> Can't locate ctime.pl in @INC (@INC contains: 
> /home/trafodion/trafodion-2.0.1/export/lib /usr/local/lib64/perl5 
> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
> ./gensq.pl line 24.



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

[jira] [Updated] (TRAFODION-1865) uninitialized buffer cause Monitor abort in CentOS 7

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1865:

Component/s: foundation

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Updated] (TRAFODION-1915) support adding/retrieving comments to SQL objects

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1915:

Priority: Minor  (was: Major)

> support adding/retrieving comments to SQL objects
> -
>
> Key: TRAFODION-1915
> URL: https://issues.apache.org/jira/browse/TRAFODION-1915
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: liu ming
>Priority: Minor
>
> It is desired to have compatible capability of Oracle's syntax to add/get 
> comments to SQL objects, like tables and columns, etc.
> QiFan give a very good initial design for this:
> 1.add a new type for column TEXT_TYPE in meta-table 
> TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
> 2.allow COMMENT ON syntax in the parser;
> 3.convert the content of COMMENT ON stmt into insertion/update of a 
> row(s) in the TEXT meta-data table for the SQL object in question;
> 4.write a UDF to show the comment easily for a SQL object, by hiding the 
> join of the meta-data TEXT and OBJECTS table.
> Can be done increamentally since there are a lot of SQL objects. And multiple 
> changes to different components.



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

[jira] [Commented] (TRAFODION-1920) suppress SQL error during HIVE_SCAN when encounter invalid value, assign null to the invalid value

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1920:
-

suppress SQL error during HIVE_SCAN when encounter invalid value, assign null 
to the invalid value
This should NOT be default behavior, Trafodion should not silently change the 
data without user's awareness.
When it is desired (By setting the CQD), HIVE_SCAN will suppress the SQL error, 
and fill value with null, and dump the error row into HDFS log file if 'log' 
option is used.

> suppress SQL error during HIVE_SCAN when encounter invalid value, assign null 
> to the invalid value
> --
>
> Key: TRAFODION-1920
> URL: https://issues.apache.org/jira/browse/TRAFODION-1920
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>




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

[jira] [Work started] (TRAFODION-1911) A special mode to be more tolerant during bulkloading and accessing HDFS raw data

[liu ming (JIRA)]

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

Work on TRAFODION-1911 started by liu ming.
---
> 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
>
> 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] [Created] (TRAFODION-1920) suppress SQL error during HIVE_SCAN when encounter invalid value, assign null to the invalid value

[liu ming (JIRA)]

liu ming created TRAFODION-1920:
---

 Summary: suppress SQL error during HIVE_SCAN when encounter 
invalid value, assign null to the invalid value
 Key: TRAFODION-1920
 URL: https://issues.apache.org/jira/browse/TRAFODION-1920
 Project: Apache Trafodion
  Issue Type: Sub-task
Reporter: liu ming






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

[jira] [Work started] (TRAFODION-1912) support automatic convert DOS format during bulkload

[liu ming (JIRA)]

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

Work on TRAFODION-1912 started by liu ming.
---
> support automatic convert DOS format during bulkload
> 
>
> Key: TRAFODION-1912
> URL: https://issues.apache.org/jira/browse/TRAFODION-1912
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>Assignee: liu ming
>
> during bulkload, if the raw text file on HDFS is in DOS format, it is desired 
> to automaticlly convert to Unix format as Trafodion requires during the load 
> process.



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

[jira] [Created] (TRAFODION-1915) support adding/retrieving comments to SQL objects

[liu ming (JIRA)]

liu ming created TRAFODION-1915:
---

 Summary: support adding/retrieving comments to SQL objects
 Key: TRAFODION-1915
 URL: https://issues.apache.org/jira/browse/TRAFODION-1915
 Project: Apache Trafodion
  Issue Type: New Feature
Reporter: liu ming


It is desired to have compatible capability of Oracle's syntax to add/get 
comments to SQL objects, like tables and columns, etc.

QiFan give a very good initial design for this:
1.  add a new type for column TEXT_TYPE in meta-table 
TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
2.  allow COMMENT ON syntax in the parser;
3.  convert the content of COMMENT ON stmt into insertion/update of a 
row(s) in the TEXT meta-data table for the SQL object in question;
4.  write a UDF to show the comment easily for a SQL object, by hiding the 
join of the meta-data TEXT and OBJECTS table.


Can be done increamentally since there are a lot of SQL objects. And multiple 
changes to different components.



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

[jira] [Created] (TRAFODION-1912) support automatic convert DOS format during bulkload

[liu ming (JIRA)]

liu ming created TRAFODION-1912:
---

 Summary: support automatic convert DOS format during bulkload
 Key: TRAFODION-1912
 URL: https://issues.apache.org/jira/browse/TRAFODION-1912
 Project: Apache Trafodion
  Issue Type: Sub-task
Reporter: liu ming


during bulkload, if the raw text file on HDFS is in DOS format, it is desired 
to automaticlly convert to Unix format as Trafodion requires during the load 
process.



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

[jira] [Assigned] (TRAFODION-1912) support automatic convert DOS format during bulkload

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1912:
---

Assignee: liu ming

> support automatic convert DOS format during bulkload
> 
>
> Key: TRAFODION-1912
> URL: https://issues.apache.org/jira/browse/TRAFODION-1912
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>Assignee: liu ming
>
> during bulkload, if the raw text file on HDFS is in DOS format, it is desired 
> to automaticlly convert to Unix format as Trafodion requires during the load 
> process.



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

[jira] [Created] (TRAFODION-1959) multiple data file in HDFS will cause bulkloader fail

[liu ming (JIRA)]

liu ming created TRAFODION-1959:
---

 Summary: multiple data file in HDFS will cause bulkloader fail
 Key: TRAFODION-1959
 URL: https://issues.apache.org/jira/browse/TRAFODION-1959
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming


reported by users several times, but I need to design a test. File a jira now 
just in case this issue will be out of track.



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

[jira] [Work started] (TRAFODION-1874) find a new way to check CLUSTER environment instead of checking pdsh

[liu ming (JIRA)]

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

Work on TRAFODION-1874 started by liu ming.
---
> 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] [Assigned] (TRAFODION-1874) find a new way to check CLUSTER environment instead of checking pdsh

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1874:
---

Assignee: liu ming

> 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] [Created] (TRAFODION-2010) UPDATE/DELETE cannot generate a parallel plan properly

[liu ming (JIRA)]

liu ming created TRAFODION-2010:
---

 Summary: UPDATE/DELETE cannot generate a parallel plan properly
 Key: TRAFODION-2010
 URL: https://issues.apache.org/jira/browse/TRAFODION-2010
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming


For big UPDATE/DELETE, that is, affecting a lot of rows, for example, 10M rows 
to update, Trafodion cannot generate a proper parallel plan by default. So very 
slow.

Reproduce steps:

DDL
CREATE TABLE T113B
  (
UNIQ INT NO DEFAULT NOT NULL 
  , C100KINT DEFAULT NULL  
  , C10K INT DEFAULT NULL  
  , C1K  INT DEFAULT NULL 
  , C100 INT DEFAULT NULL 
  , C10  INT DEFAULT NULL  
  , C1   INT DEFAULT NULL  
  , C0   INT DEFAULT NULL ,
  Primary key(uniq)
  )
  SALT USING 80 PARTITIONS
ATTRIBUTES ALIGNED FORMAT
;
 
Populate data:
upsert using load into t113b select
0 + (10 * x10) + (1 * x1) + (1000 * x1000) +
(100 * x100) + (10 * x10) +( 1 * x1),
0 + (1 * x1) + (1000 * x1000) + (100 * x100) +
(10 * x10) +( 1 * x1),
0 + (1000 * x1000) + (100 * x100) + (10 * x10) + (1 * x1),
0 + (100 * x100) + (10 * x10) + (1 * x1),
0 + (10 * x10) + (1 * x1),
0 + (1 * x1),
0,
X0
from (values(0)) t
transpose 0,1,2,3,4,5,6,7,8,9 as x10
transpose 0,1,2,3,4,5,6,7,8,9 as x1
transpose 0,1,2,3,4,5,6,7,8,9 as x1000
transpose 0,1,2,3,4,5,6,7,8,9 as x100
transpose 0,1,2,3,4,5,6,7,8,9 as x10
transpose 0,1,2,3,4,5,6,7,8,9 as x1
transpose 0,1,2,3,4,5,6,7,8,9 as x0;
 
The update DML
explain options 'f' update t113b set c0 = 0 where c1 = 0;


DELETE is similar.



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

[jira] [Assigned] (TRAFODION-762) LP Bug: 1392452 - Support new Hive data types such as CHAR

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-762:
--

Assignee: liu ming  (was: Suresh Subbiah)

> LP Bug: 1392452 - Support new Hive data types such as CHAR
> --
>
> Key: TRAFODION-762
> URL: https://issues.apache.org/jira/browse/TRAFODION-762
> Project: Apache Trafodion
>  Issue Type: Wish
>  Components: sql-cmp
>Reporter: Hans Zeller
>Assignee: liu ming
>Priority: Minor
>
> Hive now seems to support data types that match Trafodion types very well.
> According to 
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/TruncateTable
> Hive 0.11 supports DECIMAL
> Hive 0.12 supports VARCHAR
> Hive 0.13 supports CHAR, DECIMAL(precision, scale)



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

[jira] [Commented] (TRAFODION-762) LP Bug: 1392452 - Support new Hive data types such as CHAR

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-762:


I volunteer to do this. 
I want to do this incrementally, first iteration is to support DATE and 
VARCHAR, if possible.

> LP Bug: 1392452 - Support new Hive data types such as CHAR
> --
>
> Key: TRAFODION-762
> URL: https://issues.apache.org/jira/browse/TRAFODION-762
> Project: Apache Trafodion
>  Issue Type: Wish
>  Components: sql-cmp
>Reporter: Hans Zeller
>Assignee: liu ming
>Priority: Minor
>
> Hive now seems to support data types that match Trafodion types very well.
> According to 
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/TruncateTable
> Hive 0.11 supports DECIMAL
> Hive 0.12 supports VARCHAR
> Hive 0.13 supports CHAR, DECIMAL(precision, scale)



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

[jira] [Updated] (TRAFODION-1989) after uninstall, and reinstall again, dcscheck report dcs master not up

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1989:

Assignee: Amanda Moran

> after uninstall, and reinstall again, dcscheck report dcs master not up
> ---
>
> Key: TRAFODION-1989
> URL: https://issues.apache.org/jira/browse/TRAFODION-1989
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Reporter: liu ming
>Assignee: Amanda Moran
>
> in the same cluster, one install a trafodion version.
> then use trafodion_uninstaller to remove the installation.
> later at same cluster, install again via trafodion_install
> after the new installation, dcscheck fail.
> jps cannot show related DCS java processes, but those processes are up and 
> running.
> It is due to a legacy /tmp/hsperfdata_trafodion direcotry belong to the 
> previous trafodion user. The new user cannot write into this folder, but jps 
> rely on it to work correct. And dcscheck rely on jps to work correctly.
> Either installer remove that legacy directory, or uninstaller remove it. 



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

[jira] [Resolved] (TRAFODION-1920) suppress SQL error during HIVE_SCAN when encounter invalid value, assign null to the invalid value

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1920.
-
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> suppress SQL error during HIVE_SCAN when encounter invalid value, assign null 
> to the invalid value
> --
>
> Key: TRAFODION-1920
> URL: https://issues.apache.org/jira/browse/TRAFODION-1920
> Project: Apache Trafodion
>  Issue Type: Sub-task
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>




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

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1874:
-

Thanks Amanda,
I just start to work on this now. The checking is spread all over different 
scripts. Build and install. I am focusing on build issue first. For typical 
installation, PDSH will be installed first, so that is not a big issue. But for 
build system, if pdsh is installed the build will be broken, I need to fix this 
first, and figure out the relationships among various scripts.
Then we do want to update installer to use some better way to check for CLUSTER.
Trafodion does not have explicitly define installation mode like 'standalone', 
'pseudo distributed' or 'full distributed'. Maybe we should first define that.

> 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] [Created] (TRAFODION-1981) fix build issues when PDSH installed in build system

[liu ming (JIRA)]

liu ming created TRAFODION-1981:
---

 Summary: fix build issues when PDSH installed in build system
 Key: TRAFODION-1981
 URL: https://issues.apache.org/jira/browse/TRAFODION-1981
 Project: Apache Trafodion
  Issue Type: Sub-task
  Components: dev-environment
Reporter: liu ming
Assignee: liu ming
 Fix For: 2.0-incubating


if development workstation installed with pdsh, the build will broken.

there in fact only one problem when generating the error message cat file.



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

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

[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-1990) trafodion failed to initialize when using CDH , not all RS in same default region group

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1990:
-

not sure if this is duplicated jira.

> trafodion failed to initialize when using CDH , not all RS in same default 
> region group
> ---
>
> Key: TRAFODION-1990
> URL: https://issues.apache.org/jira/browse/TRAFODION-1990
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: Amanda Moran
>
> Symptom:
> SQL>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::completeAsyncOperation returned error 
> HBASE_ACCESS_ERROR(-706). Cause: 
> java.util.concurrent.ExecutionException: java.io.IOException: Coprocessor 
> result is null, retries exhausted
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> java.util.concurrent.FutureTask.get(FutureTask.java:202)
> org.trafodion.sql.HTableClient.completeAsyncOperation(HTableClient.java:1130)
> . [2015-10-23 13:50:07]
> *** ERROR[8839] Transaction was aborted. [2015-10-23 13:50:07]
>  
> Or 
>  
> >>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::rowExists returned error HBASE_ACCESS_ERROR(-705). Cause:
> java.io.IOException: Problem with calling coprocessor, no regions returned 
> result
> org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:451)
> org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:281)
> org.trafodion.sql.HBaseAccess.HTableClient.putRow(HTableClient.java:889)
> org.trafodion.sql.HBaseAccess.HTableClient.checkAndInsertRow(HTableClient.java:965)
>  
> Or
> SQL>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). 
> Cause: 
> java.io.IOException: java.lang.NullPointerException
> org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:655)
> org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:809)
> org.trafodion.sql.HTableClient.putRow(HTableClient.java:1732)
> org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1686)
> . [2016-05-11 13:38:36]
>  
> Or other like this
>  
>  
> Cause:
> The Cloudera HBase installation has more than one RegionServer configured. 
> There will be only one RegionServer Group for each RegionServer, but 
> trafodion only support one RegionServer Default Group
>  
>  
>  
>  



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

[jira] [Updated] (TRAFODION-1990) trafodion failed to initialize when using CDH , not all RS in same default region group

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1990:

Assignee: Amanda Moran

> trafodion failed to initialize when using CDH , not all RS in same default 
> region group
> ---
>
> Key: TRAFODION-1990
> URL: https://issues.apache.org/jira/browse/TRAFODION-1990
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: Amanda Moran
>
> Symptom:
> SQL>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::completeAsyncOperation returned error 
> HBASE_ACCESS_ERROR(-706). Cause: 
> java.util.concurrent.ExecutionException: java.io.IOException: Coprocessor 
> result is null, retries exhausted
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> java.util.concurrent.FutureTask.get(FutureTask.java:202)
> org.trafodion.sql.HTableClient.completeAsyncOperation(HTableClient.java:1130)
> . [2015-10-23 13:50:07]
> *** ERROR[8839] Transaction was aborted. [2015-10-23 13:50:07]
>  
> Or 
>  
> >>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::rowExists returned error HBASE_ACCESS_ERROR(-705). Cause:
> java.io.IOException: Problem with calling coprocessor, no regions returned 
> result
> org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:451)
> org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:281)
> org.trafodion.sql.HBaseAccess.HTableClient.putRow(HTableClient.java:889)
> org.trafodion.sql.HBaseAccess.HTableClient.checkAndInsertRow(HTableClient.java:965)
>  
> Or
> SQL>initialize trafodion;
>  
> *** ERROR[8448] Unable to access Hbase interface. Call to 
> ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). 
> Cause: 
> java.io.IOException: java.lang.NullPointerException
> org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:655)
> org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:809)
> org.trafodion.sql.HTableClient.putRow(HTableClient.java:1732)
> org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1686)
> . [2016-05-11 13:38:36]
>  
> Or other like this
>  
>  
> Cause:
> The Cloudera HBase installation has more than one RegionServer configured. 
> There will be only one RegionServer Group for each RegionServer, but 
> trafodion only support one RegionServer Default Group
>  
>  
>  
>  



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

[jira] [Created] (TRAFODION-1990) trafodion failed to initialize when using CDH , not all RS in same default region group

[liu ming (JIRA)]

liu ming created TRAFODION-1990:
---

 Summary: trafodion failed to initialize when using CDH , not all 
RS in same default region group
 Key: TRAFODION-1990
 URL: https://issues.apache.org/jira/browse/TRAFODION-1990
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: liu ming


Symptom:
SQL>initialize trafodion;
 
*** ERROR[8448] Unable to access Hbase interface. Call to 
ExpHbaseInterface::completeAsyncOperation returned error 
HBASE_ACCESS_ERROR(-706). Cause: 
java.util.concurrent.ExecutionException: java.io.IOException: Coprocessor 
result is null, retries exhausted
java.util.concurrent.FutureTask.report(FutureTask.java:122)
java.util.concurrent.FutureTask.get(FutureTask.java:202)
org.trafodion.sql.HTableClient.completeAsyncOperation(HTableClient.java:1130)
. [2015-10-23 13:50:07]
*** ERROR[8839] Transaction was aborted. [2015-10-23 13:50:07]
 
Or 
 
>>initialize trafodion;
 
*** ERROR[8448] Unable to access Hbase interface. Call to 
ExpHbaseInterface::rowExists returned error HBASE_ACCESS_ERROR(-705). Cause:
java.io.IOException: Problem with calling coprocessor, no regions returned 
result
org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:451)
org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:281)
org.trafodion.sql.HBaseAccess.HTableClient.putRow(HTableClient.java:889)
org.trafodion.sql.HBaseAccess.HTableClient.checkAndInsertRow(HTableClient.java:965)
 
Or
SQL>initialize trafodion;
 
*** ERROR[8448] Unable to access Hbase interface. Call to 
ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). 
Cause: 
java.io.IOException: java.lang.NullPointerException
org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:655)
org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:809)
org.trafodion.sql.HTableClient.putRow(HTableClient.java:1732)
org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1686)
. [2016-05-11 13:38:36]
 
Or other like this
 
 
Cause:
The Cloudera HBase installation has more than one RegionServer configured. 
There will be only one RegionServer Group for each RegionServer, but trafodion 
only support one RegionServer Default Group
 
 
 
 




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

[jira] [Commented] (TRAFODION-1989) after uninstall, and reinstall again, dcscheck report dcs master not up

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1989:
-

thanks Amanda,
If there is already such a handling, then no need to do further. 
We installed the R2.0 build, still have this issue. So it is solved now in 
later version, is there any other JIRA related? So I can close this one.

> after uninstall, and reinstall again, dcscheck report dcs master not up
> ---
>
> Key: TRAFODION-1989
> URL: https://issues.apache.org/jira/browse/TRAFODION-1989
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Reporter: liu ming
>Assignee: Amanda Moran
>
> in the same cluster, one install a trafodion version.
> then use trafodion_uninstaller to remove the installation.
> later at same cluster, install again via trafodion_install
> after the new installation, dcscheck fail.
> jps cannot show related DCS java processes, but those processes are up and 
> running.
> It is due to a legacy /tmp/hsperfdata_trafodion direcotry belong to the 
> previous trafodion user. The new user cannot write into this folder, but jps 
> rely on it to work correct. And dcscheck rely on jps to work correctly.
> Either installer remove that legacy directory, or uninstaller remove it. 



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

[jira] [Resolved] (TRAFODION-1981) fix build issues when PDSH installed in build system

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1981.
-
Resolution: Fixed

> fix build issues when PDSH installed in build system
> 
>
> Key: TRAFODION-1981
> URL: https://issues.apache.org/jira/browse/TRAFODION-1981
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: dev-environment
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> if development workstation installed with pdsh, the build will broken.
> there in fact only one problem when generating the error message cat file.



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

[jira] [Commented] (TRAFODION-1994) enable alter table support change column default value

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1994:
-

I tried in latest git pull code but it reports:
*** ERROR[4222] The ALTER feature is not supported in this software version.

But I know what you mean, this will be added into R2.1. I will close this when 
related code merged.

> enable alter table support change column default value
> --
>
> Key: TRAFODION-1994
> URL: https://issues.apache.org/jira/browse/TRAFODION-1994
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmu
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.1-incubating
>
>
> Enhance the 'ALTER TABLE' DDL to support change column DEFAULT setting



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

[jira] [Resolved] (TRAFODION-1557) Datasource cannot connect using Tableau

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1557.
-
Resolution: Fixed

> Datasource cannot connect using Tableau
> ---
>
> Key: TRAFODION-1557
> URL: https://issues.apache.org/jira/browse/TRAFODION-1557
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-odbc-windows
>Affects Versions: 1.2-incubating
> Environment: Windows 10 with latest Tableau version.
>Reporter: Gunnar Tapper
>Assignee: Weiqing Xu
>Priority: Critical
> Fix For: 1.2-incubating
>
>
> Configured a data source in ODBC manager. Verified via Test Connection. Tried 
> to use data source in Tableau. Does not work.



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

[jira] [Commented] (TRAFODION-1278) LP Bug: 1465899 - Create table LIKE hive table fails silently

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1278:
-

With latest build and test:

>>create table testit like hive.hive.item;

*** ERROR[1010] The statement just entered is currently not supported.

--- SQL operation failed with errors.
>>


So can we close this JIRA?

> LP Bug: 1465899 - Create table LIKE hive table fails silently
> -
>
> Key: TRAFODION-1278
> URL: https://issues.apache.org/jira/browse/TRAFODION-1278
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-general
>Reporter: Barry Fritchman
>Assignee: Qifan Chen
>Priority: Critical
> Fix For: 2.0-incubating
>
>
> When using the CREATE TABLE  LIKE  syntax with a hive table as 
> , the statement appears to execute successfully, but the table is in 
> fact not created:
> >>create table traf_orders like hive.hive.orders;
> --- SQL operation complete.
> >>invoke traf_orders;
> *** ERROR[4082] Object TRAFODION.SEABASE.TRAF_ORDERS does not exist or is 
> inaccessible.
> --- SQL operation failed with errors.
> >>
> The problem seems to occur only when a Hive table is the source.  This 
> problem causes an error when attempting to update statistics for a hive table 
> using sampling, because the sample table is not created.



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

[jira] [Resolved] (TRAFODION-1558) Tableau returns to tables or data

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1558.
-
Resolution: Fixed

> Tableau returns to tables or data
> -
>
> Key: TRAFODION-1558
> URL: https://issues.apache.org/jira/browse/TRAFODION-1558
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-odbc-windows
>Affects Versions: 1.2-incubating
> Environment: Windows 10 with latest Tableau version.
>Reporter: Gunnar Tapper
>Assignee: Weiqing Xu
>Priority: Critical
> Fix For: 1.2-incubating
>
>
> Used driver connection with TCP:/. Connection succeeded but no 
> schemas or tables are listed.



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

[jira] [Assigned] (TRAFODION-1564) Region split/balance is not being delayed if Trx Scanner obj is present

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1564:
---

Assignee: liu ming

> 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] [Assigned] (TRAFODION-1108) LP Bug: 1438467 - dtmci should return "status trans" output in JSON format

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1108:
---

Assignee: liu ming  (was: Atanu Mishra)

> 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.0-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] [Created] (TRAFODION-1999) trafodion init failed, have to remove /trafodion znode to continue

[liu ming (JIRA)]

liu ming created TRAFODION-1999:
---

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


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

[jira] [Updated] (TRAFODION-1108) LP Bug: 1438467 - dtmci should return "status trans" output in JSON format

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1108:

Fix Version/s: 2.1-incubating

> 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.0-incubating, 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] [Updated] (TRAFODION-1108) LP Bug: 1438467 - dtmci should return "status trans" output in JSON format

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1108:

Fix Version/s: (was: 2.0-incubating)

> 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] [Commented] (TRAFODION-1914) optimize "added columns" in indexes

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1914:
-

Hi, Eric,
I filed JIRA 1976
Trafodion support to create 'unique index'. In that case, one should make sure 
the index column value will be unique. Then that index will not have primary 
key list into clustering key.
This is already supported but not documented.

So this seems like a solved issue?

> optimize "added columns" in indexes
> ---
>
> Key: TRAFODION-1914
> URL: https://issues.apache.org/jira/browse/TRAFODION-1914
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Reporter: Eric Owhadi
>
> the current CREATE INDEX feature will always put each column added to the 
> index in the clustering key. But sometimes, users just want to add columns to 
> the index to avoid having to probe back the primary table to fetch just one 
> or 2 column back. Instead copying these columns in the index can avoid making 
> a probe back to main table and therefore improve performance. Current 
> implementation allows this, but will always put the extra column as part of 
> the clustering key. That is not optimal, and very bad for the case of 
> VARCHAR, since they are exploded to there max size when part of the 
> clustering key. So this JIRA is abount altering the syntax of create index, 
> and flag columns that are added but should not be part of the clustering key.



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

[jira] [Commented] (TRAFODION-1914) optimize "added columns" in indexes

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1914:
-

>>create table ut1 ( c1 int not null, c2 int not null, primary key (c1) );

--- SQL operation complete.
>>insert into ut1 Values(1,1);

--- 1 row(s) inserted.
>>create unique index ui1 on ut1(c2);

--- SQL operation complete.
>>exit

then use hbase shell
hbase(main):002:0> scan  'TRAFODION.SEABASE.UI1'
ROWCOLUMN+CELL
 \x80\x00\x00\x01  column=#1:\x01, 
timestamp=1463582407513, 
value=\x08\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x01\x00\x00\x00
1 row(s) in 0.0800 seconds


> optimize "added columns" in indexes
> ---
>
> Key: TRAFODION-1914
> URL: https://issues.apache.org/jira/browse/TRAFODION-1914
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Reporter: Eric Owhadi
>
> the current CREATE INDEX feature will always put each column added to the 
> index in the clustering key. But sometimes, users just want to add columns to 
> the index to avoid having to probe back the primary table to fetch just one 
> or 2 column back. Instead copying these columns in the index can avoid making 
> a probe back to main table and therefore improve performance. Current 
> implementation allows this, but will always put the extra column as part of 
> the clustering key. That is not optimal, and very bad for the case of 
> VARCHAR, since they are exploded to there max size when part of the 
> clustering key. So this JIRA is abount altering the syntax of create index, 
> and flag columns that are added but should not be part of the clustering key.



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

[jira] [Resolved] (TRAFODION-209) LP Bug: 1298673 - Monitor expects node names to have characters that are only lowercase

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-209.

Resolution: Fixed

> LP Bug: 1298673 - Monitor expects node names to have characters that are only 
> lowercase
> ---
>
> Key: TRAFODION-209
> URL: https://issues.apache.org/jira/browse/TRAFODION-209
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Joanie Cooper
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> You can create node names for example "Joanie-vm-1" in the HP Cloud.  When 
> you install trafodion, the appropriate "sqconfig" and "cluster.conf" file 
> entries correctly indicate the node name "Joanie-vm-1".  However, when the 
> monitor is launched, internally, it has shifted the name to be all lowercase, 
> e.g. "joanie-vm-1".  This causes the monitor initialization to fail and 
> trafodion can not start.  There are no monitor core files generated.  This 
> was analyzed via "gdb" as the monitor process was initializing.  The 
> workaround is to specify that all node names must  use lowercase characters.



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

[jira] [Commented] (TRAFODION-1632) Hive scan on wide tables with several string type columns causes SIGSEGV

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1632:
-

create table  Input_10_TestClientData  
(
 sourcehistoryuid bigint
,importdate timestamp
,filedate timestamp
,exclusionindicator tinyint
,DataCategory STRING
,TransactionReferenceNumber STRING
,ReportStatus STRING
,ReporterIDType STRING
,ReporterID STRING
,SubmitterIDType STRING
,SubmitterID STRING
,Buyer_ID_Type STRING
,Buyer_ID STRING
,BuyerCountryofBranch STRING
,BuyerFirstName STRING
,BuyerSurname STRING
,BuyerDOB STRING
,BuyerCountryofResidence STRING
,BuyerPostCode STRING
,BuyerDecisionMakerIDType STRING
,BuyerDecisionMakerID STRING
,BuyerDecisionMakerFirstName STRING
,BuyerDecisionMakerSurname STRING
,BuyerDecisionMakerDOB STRING
,BuyerDecisionMakerCountryofResidence STRING
,BuyerDecisionMakerPostCode STRING
,SellerIDType STRING
,SellerID STRING
,SellerCountryofBranch STRING
,SellerFirstName STRING
,SellerSurname STRING
,SellerDOB STRING
,SellerCountryofResidence STRING
,SellerPostCode STRING
,SellerDecisionMakerIDType STRING
,SellerDecisionMakerID STRING
,SellerDecisionMakerFirstName STRING
,SellerDecisionMakerSurname STRING
,SellerDecisionMakerDOB STRING
,SellerDecisionMakerCountryofResidence STRING
,SellerDecisionMakerPostCode STRING
,OrderTransmissionIndicator STRING
,BuyerTransmitterIDType STRING
,BuyerTransmitterID STRING
,SellerTransmitterIDType STRING
,SellerTransmitterID STRING
,TradingDate STRING
,TradingTime STRING
,TradingCapacity STRING
,Quantity STRING
,QuantityNotation STRING
,Price STRING
,PriceNotation STRING
,Currency1 STRING
,Currency2 STRING
,PriceMultiplier STRING
,Consideration STRING
,Venue STRING
,ExecutingCountryofBranch STRING
,InstrumentIDType STRING
,InstrumentID STRING
,InstrumentClassificationType STRING
,InstrumentClassification STRING
,UnderlyingInstrumentIDType STRING
,UnderlyingInstrumentID STRING
,PutCall STRING
,StrikePrice STRING
,OptionStyle STRING
,MaturityDate STRING
,ResultofExercise STRING
,DeliveryType STRING
,UpFrontPayment STRING
,UpFrontPaymentCurrency STRING
,ContractModificationType STRING
,InvestmentTraderIDType STRING
,InvestmentTraderID STRING
,InvestmentTraderCountryofBranch STRING
,ExecutionTraderIDType STRING
,ExecutionTraderID STRING
,ExecutionTraderCountryofBranch STRING
,InvestmentAlgorithmID STRING
,ExecutionAlgorithmID STRING
,WaiverIndicator STRING
,ShortSellingIndicator STRING
,OTCPostTradeIndicator STRING
,CommodityDerivativeIndicator STRING
,ReloadSourceHistoryUID STRING
) ;

will pass Hive syntax checking

> Hive scan on wide tables with several string type columns causes SIGSEGV 
> -
>
> Key: TRAFODION-1632
> URL: https://issues.apache.org/jira/browse/TRAFODION-1632
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-exe
>Affects Versions: 1.3-incubating
>Reporter: Suresh Subbiah
> Attachments: hs_err_pid54160.log
>
>
> This query caused a process abort.
> select * from hive.hive."Input_10_TestClientData_1" limit 10;
> Table has 88 columns and 100K rows
> Hive DDL is
> create table "Input_10_TestClientData" (
>   ,"sourcehistoryuid" bigint
>   ,"importdate" timestamp
>   ,"filedate" timestamp
>   ,"exclusionindicator" tinyint
>   ,"Data Category" STRING
>   ,"Transaction Reference Number" STRING
>   ,"Report Status" STRING
>   ,"Reporter ID Type" STRING
>   ,"Reporter ID" STRING
>   ,"Submitter ID Type" STRING
>   ,"Submitter ID" STRING
>   ,"Buyer ID Type" STRING
>   ,"Buyer ID" STRING
>   ,"Buyer Country of Branch" STRING
>   ,"Buyer First Name" STRING
>   ,"Buyer Surname" STRING
>   ,"Buyer DOB" STRING
>   ,"Buyer Country of Residence" STRING
>   ,"Buyer Post Code" STRING
>   ,"Buyer Decision Maker ID Type" STRING
>   ,"Buyer Decision Maker ID" STRING
>   ,"Buyer Decision Maker First Name" STRING
>   ,"Buyer Decision Maker Surname" STRING
>   ,"Buyer Decision Maker DOB" STRING
>   ,"Buyer Decision Maker Country of Residence" STRING
>   ,"Buyer Decision Maker Post Code" STRING
>   ,"Seller ID Type" STRING
>   ,"Seller ID" STRING
>   ,"Seller Country of Branch" STRING
>   ,"Seller First Name" STRING
>   ,"Seller Surname" STRING
>   ,"Seller DOB" STRING
>   ,"Seller Country of Residence" STRING
>   ,"Seller Post Code" STRING
>   ,"Seller Decision Maker ID Type" STRING
>   ,"Seller Decision Maker ID" STRING
>   ,"Seller Decision Maker First Name" STRING
>   ,"Seller Decision Maker Surname" STRING
>   ,"Seller Decision Maker DOB" STRING
>   ,"Seller Decision Maker Country of Residence" STRING
>   ,"Seller Decision Maker Post Code" STRING
>   ,"Order Transmission 

[jira] [Assigned] (TRAFODION-209) LP Bug: 1298673 - Monitor expects node names to have characters that are only lowercase

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-209:
--

Assignee: liu ming  (was: Atanu Mishra)

> LP Bug: 1298673 - Monitor expects node names to have characters that are only 
> lowercase
> ---
>
> Key: TRAFODION-209
> URL: https://issues.apache.org/jira/browse/TRAFODION-209
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Joanie Cooper
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> You can create node names for example "Joanie-vm-1" in the HP Cloud.  When 
> you install trafodion, the appropriate "sqconfig" and "cluster.conf" file 
> entries correctly indicate the node name "Joanie-vm-1".  However, when the 
> monitor is launched, internally, it has shifted the name to be all lowercase, 
> e.g. "joanie-vm-1".  This causes the monitor initialization to fail and 
> trafodion can not start.  There are no monitor core files generated.  This 
> was analyzed via "gdb" as the monitor process was initializing.  The 
> workaround is to specify that all node names must  use lowercase characters.



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

[jira] [Commented] (TRAFODION-209) LP Bug: 1298673 - Monitor expects node names to have characters that are only lowercase

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-209:


solved by TRAFODION-1854

> LP Bug: 1298673 - Monitor expects node names to have characters that are only 
> lowercase
> ---
>
> Key: TRAFODION-209
> URL: https://issues.apache.org/jira/browse/TRAFODION-209
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Joanie Cooper
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> You can create node names for example "Joanie-vm-1" in the HP Cloud.  When 
> you install trafodion, the appropriate "sqconfig" and "cluster.conf" file 
> entries correctly indicate the node name "Joanie-vm-1".  However, when the 
> monitor is launched, internally, it has shifted the name to be all lowercase, 
> e.g. "joanie-vm-1".  This causes the monitor initialization to fail and 
> trafodion can not start.  There are no monitor core files generated.  This 
> was analyzed via "gdb" as the monitor process was initializing.  The 
> workaround is to specify that all node names must  use lowercase characters.



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

[jira] [Commented] (TRAFODION-1914) optimize "added columns" in indexes

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1914:
-

yes, I see. 
It is like 'covered index'. A new syntax should be invented. unique index 
cannot support this. 
this must be added as a new feature, yes, it makes sense.
thanks,
Ming

> optimize "added columns" in indexes
> ---
>
> Key: TRAFODION-1914
> URL: https://issues.apache.org/jira/browse/TRAFODION-1914
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Reporter: Eric Owhadi
>
> the current CREATE INDEX feature will always put each column added to the 
> index in the clustering key. But sometimes, users just want to add columns to 
> the index to avoid having to probe back the primary table to fetch just one 
> or 2 column back. Instead copying these columns in the index can avoid making 
> a probe back to main table and therefore improve performance. Current 
> implementation allows this, but will always put the extra column as part of 
> the clustering key. That is not optimal, and very bad for the case of 
> VARCHAR, since they are exploded to there max size when part of the 
> clustering key. So this JIRA is abount altering the syntax of create index, 
> and flag columns that are added but should not be part of the clustering key.



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

[jira] [Created] (TRAFODION-1989) after uninstall, and reinstall again, dcscheck report dcs master not up

[liu ming (JIRA)]

liu ming created TRAFODION-1989:
---

 Summary: after uninstall, and reinstall again, dcscheck report dcs 
master not up
 Key: TRAFODION-1989
 URL: https://issues.apache.org/jira/browse/TRAFODION-1989
 Project: Apache Trafodion
  Issue Type: Bug
  Components: installer
Reporter: liu ming


in the same cluster, one install a trafodion version.
then use trafodion_uninstaller to remove the installation.
later at same cluster, install again via trafodion_install
after the new installation, dcscheck fail.

jps cannot show related DCS java processes, but those processes are up and 
running.

It is due to a legacy /tmp/hsperfdata_trafodion direcotry belong to the 
previous trafodion user. The new user cannot write into this folder, but jps 
rely on it to work correct. And dcscheck rely on jps to work correctly.

Either installer remove that legacy directory, or uninstaller remove it. 



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

[jira] [Created] (TRAFODION-1994) enable alter table support change column default value

[liu ming (JIRA)]

liu ming created TRAFODION-1994:
---

 Summary: enable alter table support change column default value
 Key: TRAFODION-1994
 URL: https://issues.apache.org/jira/browse/TRAFODION-1994
 Project: Apache Trafodion
  Issue Type: Improvement
  Components: sql-cmu
Reporter: liu ming
 Fix For: 2.1-incubating


Enhance the 'ALTER TABLE' DDL to support change column DEFAULT setting



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

[jira] [Assigned] (TRAFODION-1994) enable alter table support change column default value

[liu ming (JIRA)]

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

liu ming reassigned TRAFODION-1994:
---

Assignee: liu ming

> enable alter table support change column default value
> --
>
> Key: TRAFODION-1994
> URL: https://issues.apache.org/jira/browse/TRAFODION-1994
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmu
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.1-incubating
>
>
> Enhance the 'ALTER TABLE' DDL to support change column DEFAULT setting



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

[jira] [Commented] (TRAFODION-1994) enable alter table support change column default value

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1994:
-

Sometimes after table created, one want to change the table column definition 
to have different default value. 
It will be good to have this implemented.

create table altert3 (c1 int, c2 int, c3 int);
alter table altert3 alter column c3 default 1;
--set the default value of column c3 to 1




> enable alter table support change column default value
> --
>
> Key: TRAFODION-1994
> URL: https://issues.apache.org/jira/browse/TRAFODION-1994
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmu
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.1-incubating
>
>
> Enhance the 'ALTER TABLE' DDL to support change column DEFAULT setting



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

[jira] [Work started] (TRAFODION-1994) enable alter table support change column default value

[liu ming (JIRA)]

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

Work on TRAFODION-1994 started by liu ming.
---
> enable alter table support change column default value
> --
>
> Key: TRAFODION-1994
> URL: https://issues.apache.org/jira/browse/TRAFODION-1994
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmu
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.1-incubating
>
>
> Enhance the 'ALTER TABLE' DDL to support change column DEFAULT setting



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

[jira] [Commented] (TRAFODION-1959) multiple data file in HDFS will cause bulkloader fail

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1959:
-

core dump info:
#0  0x003892432625 in raise () from /lib64/libc.so.6
#1  0x003892433e05 in abort () from /lib64/libc.so.6
#2  0x7f345f2b2785 in ?? () from 
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/jre/lib/amd64/server/libjvm.so
#3  0x7f345f42603f in ?? () from 
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/jre/lib/amd64/server/libjvm.so
#4  0x7f345f2b7322 in JVM_handle_linux_signal ()
   from 
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/jre/lib/amd64/server/libjvm.so
#5  
#6  _M_data (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/basic_string.h:278
#7  _M_rep (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/basic_string.h:286
#8  size (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/basic_string.h:629
#9  compare (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/basic_string.h:2021
#10 operator<  
(this=0x20b0b40,
file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366", 
type=Lob_Cursor_Simple,
range=939524096, bufMaxSize=67108864, maxBytes=56803570, waited=0, 
lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/basic_string.h:2317
#11 operator() (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/stl_function.h:230
#12 _M_lower_bound (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/stl_tree.h:986
#13 find (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/stl_tree.h:1421
#14 find (this=0x20b0b40, file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366",
type=Lob_Cursor_Simple, range=939524096, bufMaxSize=67108864, 
maxBytes=56803570, waited=0, lobGlobals=0xc7c8c0)
at 
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/stl_map.h:659
#15 ExLob::openDataCursor (this=0x20b0b40,
file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366", 
type=Lob_Cursor_Simple,
range=939524096, bufMaxSize=67108864, maxBytes=56803570, waited=0, 
lobGlobals=0xc7c8c0) at ../exp/ExpLOBaccess.cpp:1074
#16 0x7f3460dd4783 in ExLobGlobals::processPreOpens (this=0xc7c8c0) at 
../exp/ExpLOBaccess.cpp:3123
#17 0x7f3460dd4b09 in ExLobGlobals::performRequest (this=0xc7c8c0, 
request=)
at ../exp/ExpLOBaccess.cpp:2651
#18 0x7f3460dd4cb9 in ExLobGlobals::doWorkInThread (this=0xc7c8c0) at 
../exp/ExpLOBaccess.cpp:3087
---Type  to continue, or q  to quit---
#19 0x7f3460dd4d09 in workerThreadMain (arg=) at 
../exp/ExpLOBaccess.cpp:2867
#20 0x003892807a51 in start_thread () from /lib64/libpthread.so.0
#21 0x0038924e893d in clone () from /lib64/libc.so.6
 
(gdb) frame 15
#15 ExLob::openDataCursor (this=0x20b0b40,
file=0x7f344bc149f8 
"hdfs://esg06.esgyncn.local:8020/px/td/devices_94075.txt:7f34546e4d98:366", 
type=Lob_Cursor_Simple,
range=939524096, bufMaxSize=67108864, 

[jira] [Updated] (TRAFODION-1959) multiple data file in HDFS will cause bulkloader fail

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1959:

Assignee: Selvaganesan Govindarajan

> multiple data file in HDFS will cause bulkloader fail
> -
>
> Key: TRAFODION-1959
> URL: https://issues.apache.org/jira/browse/TRAFODION-1959
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: Selvaganesan Govindarajan
>
> reported by users several times, but I need to design a test. File a jira now 
> just in case this issue will be out of track.



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

[jira] [Updated] (TRAFODION-1952) jdbc can not work without config hostname and ip in /etc/hosts on client machine

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1952:

Assignee: Kevin Xu

> jdbc can not work without config hostname and ip in /etc/hosts on client 
> machine
> 
>
> Key: TRAFODION-1952
> URL: https://issues.apache.org/jira/browse/TRAFODION-1952
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-jdbc-t4
>Affects Versions: 1.3-incubating
> Environment: client machine Linux
>Reporter: Feng Qiang
>Assignee: Kevin Xu
>Priority: Minor
>
> An error occurred while establishing the connection:
> Long Message:
> *** ERROR[29717] Internal error: Error getting the name of the local host.
> Details:
>Type: org.trafodion.jdbc.t4.SecurityException
>Error Code: 29717
>SQL State: 38001



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

[jira] [Commented] (TRAFODION-1961) An empty string in HIVE shouldn't be treated as NULL in Trafodion

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-1961:
-

Hi, Selva,
What empty string means here?
If a text data file delimited with '|' and have 3 columns:
a|b|c
a||c
the first will have ('a'), ('b'), ('c')
the second row will have ('a'), null, ('c')
I feel this is normal?

thanks,
Ming

> An empty string in HIVE  shouldn't be treated as NULL in Trafodion
> --
>
> Key: TRAFODION-1961
> URL: https://issues.apache.org/jira/browse/TRAFODION-1961
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Selvaganesan Govindarajan
>
> Hive table select
> hive> select * from nulls ;
> OK
> nulls.a   nulls.b
> NULL  a
> NULL  a
> aaa1  b1
>   b2
> aaa3  
> aaa5  
>   b6
> When this table is accessed from Trafodion, the empty string is treated as 
> NULL
> >>cqd hive_max_string_length '10' ;
> --- SQL operation complete.
> >>fc sele
> >>select * from hive.hive.nulls ;
> ..
> A   B 
> --  --
> ?   a 
> ?   a 
> aaa1b1
> ?   b2
> aaa3? 
> ?   ? 
> aaa5? 
> ?   b6
> Need a CQD to provide backward compatibility with the old behavior. 



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

[jira] [Created] (TRAFODION-1976) SQL reference manual should add description of the 'create unique index' syntax

[liu ming (JIRA)]

liu ming created TRAFODION-1976:
---

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


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] [Updated] (TRAFODION-1969) support Oracle's TRUNCATE TABLE syntax

[liu ming (JIRA)]

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

liu ming updated TRAFODION-1969:

Assignee: taian.wei

> support Oracle's TRUNCATE TABLE syntax 
> ---
>
> Key: TRAFODION-1969
> URL: https://issues.apache.org/jira/browse/TRAFODION-1969
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: liu ming
>Assignee: taian.wei
>
> Oracle 'TRUNCATE TABLE' is used to delete all data for a given table.
> It should be the same command in Trafodion 'purgedata'.
> It will be convenient that Trafodion directly support this syntax.



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

[jira] [Created] (TRAFODION-1969) support Oracle's TRUNCATE TABLE syntax

[liu ming (JIRA)]

liu ming created TRAFODION-1969:
---

 Summary: support Oracle's TRUNCATE TABLE syntax 
 Key: TRAFODION-1969
 URL: https://issues.apache.org/jira/browse/TRAFODION-1969
 Project: Apache Trafodion
  Issue Type: Improvement
Reporter: liu ming


Oracle 'TRUNCATE TABLE' is used to delete all data for a given table.
It should be the same command in Trafodion 'purgedata'.

It will be convenient that Trafodion directly support this syntax.



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

[jira] [Commented] (TRAFODION-2047) add SQL syntax support to INTERSECT

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-2047:
-

As Hans correctly pointed out, it is hard to support 'INTERSECT ALL' at 
present, so this JIRA will only add support for 'INTERSECT' or 'INTERSECT 
DISTINCT', and raise syntax error for 'INTERSECT ALL'
A new JIRA will be created to cover 'INTERSECT ALL' later.

> 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-1605) sqstart hangs if ulimits not correct

[liu ming (JIRA)]

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

liu ming resolved TRAFODION-1605.
-
   Resolution: Fixed
Fix Version/s: 2.1-incubating

> 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
> Fix For: 2.1-incubating
>
>
> 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] [Work started] (TRAFODION-2090) improve the very first time of query compiling

[liu ming (JIRA)]

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

Work on TRAFODION-2090 started 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
>
> 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] [Commented] (TRAFODION-2066) Not allowing Order By the aggregation, except when named

[liu ming (JIRA)]

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

liu ming commented on TRAFODION-2066:
-

This feature is already supported, one need to turn on the CQD mode_special_4 
to enable it.
But more generic, some database support more flexible order by syntax, that the 
order by expression can be a random expression. This JIRA may change to support 
that kind of order by feature.

> 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)