[jira] [Created] (TRAFODION-2065) Documentation of TO_CHAR, TO_DATE, TO_NUMBER

2016-06-15 Thread liu ming (JIRA) 
liu ming created TRAFODION-2065:
---

 Summary: Documentation of TO_CHAR, TO_DATE, TO_NUMBER
 Key: TRAFODION-2065
 URL: https://issues.apache.org/jira/browse/TRAFODION-2065
 Project: Apache Trafodion
  Issue Type: Bug
  Components: documentation
Reporter: liu ming


It is very hard to know how to use Trafodion TO_CHAR, the format is not fully 
compatible with Oracle, and there are some limitations, without documentation, 
it is hard to be used.



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

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

2016-06-15 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user traflm opened a pull request:

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

[TRAFODION-1745] show more related info when TRANSLATE run into SQL E…

…rror

Show what is the translation: from which charset to what charset, and 
showing the offending data in HEX mode.
This will help troubleshooting.

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

$ git pull https://github.com/traflm/incubator-trafodion TRAFODION-2046-1

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

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

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

This closes #547


commit 4934fdec0bc98aa037db5793366ab8600e544f58
Author: Liu Ming 
Date:   2016-06-16T02:17:18Z

[TRAFODION-1745] show more related info when TRANSLATE run into SQL Error




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



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

[jira] [Work started] (TRAFODION-1676) support better runtime error message when a SQL function meet fital error

2016-06-15 Thread liu ming (JIRA) 

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

Work on TRAFODION-1676 started by liu ming.
---
> support better runtime error message when a SQL function meet fital error
> -
>
> Key: TRAFODION-1676
> URL: https://issues.apache.org/jira/browse/TRAFODION-1676
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
>
> A sql contains some SQL function, for example UPPER(), when the input data of 
> UPPER() contains invalid data, UPPER() will fail. In this case, the whole 
> query abort, and the error message cannot tell which row has invalid data, so 
> it is very hard to fix the problem.
> It will be good to have row id or the real value of the error row in the 
> error message to help trouble shooting.



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

[jira] [Comment Edited] (TRAFODION-1676) support better runtime error message when a SQL function meet fital error

2016-06-15 Thread liu ming (JIRA) 

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

liu ming edited comment on TRAFODION-1676 at 6/16/16 2:10 AM:
--

The first improvement can be done in hive_scan.
It seems only SCAN operator knows the line number, or row id of a given row. 

One general improvement can be to add messages to show which column the data is 
related. And this column indication is required in field now.


was (Author: ovis_poly):
The first improvement can be done in hive_scan.
It seems only SCAN operator knows the line number, or row id of a given row. 

One general improvement can be to add messages to show which column the data is 
related.

> support better runtime error message when a SQL function meet fital error
> -
>
> Key: TRAFODION-1676
> URL: https://issues.apache.org/jira/browse/TRAFODION-1676
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
>
> A sql contains some SQL function, for example UPPER(), when the input data of 
> UPPER() contains invalid data, UPPER() will fail. In this case, the whole 
> query abort, and the error message cannot tell which row has invalid data, so 
> it is very hard to fix the problem.
> It will be good to have row id or the real value of the error row in the 
> error message to help trouble shooting.



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

[jira] [Commented] (TRAFODION-1676) support better runtime error message when a SQL function meet fital error

2016-06-15 Thread liu ming (JIRA) 

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

liu ming commented on TRAFODION-1676:
-

The first improvement can be done in hive_scan.
It seems only SCAN operator knows the line number, or row id of a given row. 

One general improvement can be to add messages to show which column the data is 
related.

> support better runtime error message when a SQL function meet fital error
> -
>
> Key: TRAFODION-1676
> URL: https://issues.apache.org/jira/browse/TRAFODION-1676
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Reporter: liu ming
>Assignee: liu ming
>Priority: Minor
>
> A sql contains some SQL function, for example UPPER(), when the input data of 
> UPPER() contains invalid data, UPPER() will fail. In this case, the whole 
> query abort, and the error message cannot tell which row has invalid data, so 
> it is very hard to fix the problem.
> It will be good to have row id or the real value of the error row in the 
> error message to help trouble shooting.



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

[jira] [Created] (TRAFODION-2064) Provisioning Guide needs to be updated for Trafodion 2.0

2016-06-15 Thread David Wayne Birdsall (JIRA) 
David Wayne Birdsall created TRAFODION-2064:
---

 Summary: Provisioning Guide needs to be updated for Trafodion 2.0
 Key: TRAFODION-2064
 URL: https://issues.apache.org/jira/browse/TRAFODION-2064
 Project: Apache Trafodion
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.0-incubating
 Environment: N/A
Reporter: David Wayne Birdsall


Among the things that need addressing are:

Add the date for Release 2.0

Mention that Release 2.0 supports CDH 5.4 and not earlier releases (and 
similarly as appropriate for HDP).

Probably worth doing a read-through of the guide to see what else needs 
updating.



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

[jira] [Commented] (TRAFODION-2048) Improve checks during Trafodion Kerberos Installation

2016-06-15 Thread ASF GitHub Bot (JIRA) 

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

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

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

https://github.com/apache/incubator-trafodion/pull/546#discussion_r67192402
  
--- Diff: core/sqf/sql/scripts/sqstart ---
@@ -220,6 +220,31 @@ function SQCheckOrphanProcesses {
 
 }
 
+function checkKerberos {
+
+   # Check to see if kerberos is enabled in Hadoop
+   cat /etc/hadoop/conf/core-site.xml | while read a; do
+ found=`echo $a | grep "hadoop.security.authentication" | wc -l`
+ if [[ $found -eq 1 ]]; then
+   read b
+   enabled=`echo $b | grep kerberos | wc -l`
--- End diff --

I want to improve the check to see if Kerberos is enabled in general.  
There is the issue you mention above and in a customer environment, core-site 
may not be in the default location (take install_local_hadoop for instance).   
With a different solution, I hope to avoid scanning core-site.   I did write up 
a JIRA to improve this (TRAFODION-2048).


> Improve checks during Trafodion Kerberos Installation
> -
>
> Key: TRAFODION-2048
> URL: https://issues.apache.org/jira/browse/TRAFODION-2048
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: sql-security
>Reporter: Roberta Marton
>Assignee: Roberta Marton
> Fix For: 1.1 (pre-incubation)
>
>
> Add checks for security configuration issues at the same time other config 
> problems are checked (traf_config_check). Today problems are not discovered 
> until late in the process.  When problems are found, it is not always easy to 
> figure out the issue.  Checks to include:
> -> valid KDC server and LDAP server
> -> valid KDC admin user and password
> -> LDAP user to be associated with database user ROOT is valid
> Also, remove the hard coded location for the Hadoop's core-site.xml file.  
> Some installations may not be using the standard location.



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

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

2016-06-15 Thread David Wayne Birdsall (JIRA) 

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

David Wayne Birdsall commented on TRAFODION-1841:
-

Agree; I cannot reproduce it either. I will guess that it was something 
peculiar to my development instance at that time. Feel free to close as not 
reproduceable.

> 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] [Commented] (TRAFODION-2044) CREATE TABLE LIKE with SALT USING clause uses source table partition count

2016-06-15 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> CREATE TABLE LIKE with SALT USING  clause uses source table partition count
> ---
>
> Key: TRAFODION-2044
> URL: https://issues.apache.org/jira/browse/TRAFODION-2044
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmu
>Affects Versions: 2.0-incubating
> Environment: Trafodion 2.0 environment
>Reporter: Carol Pearson
>Assignee: David Wayne Birdsall
> Fix For: 2.1-incubating
>
>
> Using CREATE TABLE LIKE to create a table, then changing the number of 
> partitions. The resulting new table number of partitions matches the 
> partitioncount for the source table in the CREATE TABLE LIKE statement, 
> rather than the value specified in the command:
> See the following commands:
> >>>create table tsource (c1 int not null, c2 int not null, primary key (c1))
> +>salt using 4 partitions;
> --- SQL operation complete.
> >>create table tsource_like like tsource salt using 8 partitions;
> --- SQL operation complete.
> >>showddl tsource_like
> +>;
> CREATE TABLE TRAFODION.SEABASE.TSOURCE_LIKE
>   (
> C1   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , C2   INT NO DEFAULT NOT NULL NOT DROPPABLE
>   SERIALIZED
>   , PRIMARY KEY (C1 ASC)
>   )
>   SALT USING 4 PARTITIONS
> ;
> --- SQL operation complete.
> >>
> But table tsource_like was created using SALT USING 8 PARTITIONS



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

[jira] [Closed] (TRAFODION-1617) Improvement in some scripts for startup

2016-06-15 Thread liu ming (JIRA) 

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

liu ming closed TRAFODION-1617.
---
Resolution: Fixed

> Improvement in some scripts for startup
> ---
>
> Key: TRAFODION-1617
> URL: https://issues.apache.org/jira/browse/TRAFODION-1617
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: dev-environment
>Affects Versions: 2.0-incubating
>Reporter: Narendra
>Priority: Minor
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Add scripts and supporting Java code to help with the startup and setup of a 
> dev env.



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

[jira] [Resolved] (TRAFODION-2046) change DTM's memoryUsageChore default settings to enable memory threthold

2016-06-15 Thread liu ming (JIRA) 

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

liu ming resolved TRAFODION-2046.
-
Resolution: Fixed

> change DTM's memoryUsageChore default settings to enable memory threthold
> -
>
> Key: TRAFODION-2046
> URL: https://issues.apache.org/jira/browse/TRAFODION-2046
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: liu ming
>Assignee: liu ming
>
> DTM provide MemoryUsageChore to monitor the memory pressure in a 
> RegionServer, when memory is beyond a defined threshold, it will give a 
> warning or prevent new operations based on a flag.
> By default, the threshold is now 100%, and the flag is just warning. So that 
> means DTM coprocessor can use all RS memory and when it find memory pressure 
> , just print warning, instead of control new transaction.
> This will lead to un-predictable behavior for certain fat transaction.
> It is better to change the default setting to enable protection.



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

[jira] [Commented] (TRAFODION-1617) Improvement in some scripts for startup

2016-06-15 Thread Narendra Goyal (JIRA) 

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

Narendra Goyal commented on TRAFODION-1617:
---

Anyone with the power - please close this JIRA :) thanks!

> Improvement in some scripts for startup
> ---
>
> Key: TRAFODION-1617
> URL: https://issues.apache.org/jira/browse/TRAFODION-1617
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: dev-environment
>Affects Versions: 2.0-incubating
>Reporter: Narendra
>Priority: Minor
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Add scripts and supporting Java code to help with the startup and setup of a 
> dev env.



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