[jira] [Commented] (TRAFODION-2183) ckillall should remove the confused warning message
[ https://issues.apache.org/jira/browse/TRAFODION-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434132#comment-15434132 ] ASF GitHub Bot commented on TRAFODION-2183: --- GitHub user mkby opened a pull request: https://github.com/apache/incubator-trafodion/pull/670 [TRAFODION-2183] remove warning in ckillall ckillall should remove the confused warning message You can merge this pull request into a Git repository by running: $ git pull https://github.com/mkby/incubator-trafodion master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/670.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 #670 commit 5743270c88b3fc0db7fad81a411f7a720eb9af43 Author: Eason Date: 2016-08-24T03:36:11Z [TRAFODION-2183] remove warning in ckillall ckillall should remove the confused warning message > ckillall should remove the confused warning message > --- > > Key: TRAFODION-2183 > URL: https://issues.apache.org/jira/browse/TRAFODION-2183 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: Eason Zhang >Assignee: Eason Zhang >Priority: Minor > > Now ckillall will not damage the data, it should remove the warning message > below: > "This command might cause irreparable damage to your database" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2183) ckillall should remove the confused warning message
Eason Zhang created TRAFODION-2183: -- Summary: ckillall should remove the confused warning message Key: TRAFODION-2183 URL: https://issues.apache.org/jira/browse/TRAFODION-2183 Project: Apache Trafodion Issue Type: Improvement Reporter: Eason Zhang Assignee: Eason Zhang Priority: Minor Now ckillall will not damage the data, it should remove the warning message below: "This command might cause irreparable damage to your database" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2182) JVM exception for TMUDF
David Wong created TRAFODION-2182: - Summary: JVM exception for TMUDF Key: TRAFODION-2182 URL: https://issues.apache.org/jira/browse/TRAFODION-2182 Project: Apache Trafodion Issue Type: Bug Components: foundation Affects Versions: 2.1-incubating Environment: TMUDF Reporter: David Wong Fix For: 2.1-incubating This involved jar file containing Lucene components for TMUDF. When run the TMUDF, get... *** ERROR[11224] The Java virtual machine raised an exception. Details: java.lang.IllegalArgumentException: An SPI class of type org.apache.lucene.codecs.Codec with name 'Lucene60' does not exist. You need to add the corresponding JAR file supporting this SPI to your classpath. The current classpath supports the following names: [] [2016-08-23 16:56:47] Add jar to CLASSPATH in $MY_SQROOT/etc/ms.env is a workaround (didn't need to bounce anything). Exception does not occur. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1907) Check for passwordless ssh
[ https://issues.apache.org/jira/browse/TRAFODION-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-1907. - Resolution: Fixed This is required for Trafodion user id and is fixed. For installer user id, this is not a requirement. If a user wants to set this up, they can use acceptKeys located in the installer directory. > Check for passwordless ssh > -- > > Key: TRAFODION-1907 > URL: https://issues.apache.org/jira/browse/TRAFODION-1907 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Amanda Moran >Assignee: Amanda Moran > > Currently have a check for passwordless ssh but only fowards... not a > "backwards" check. > Check that node1 can get to node2 and node3 but not that node3 can get to > node2 or node1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1565) Remove check for pdsh on single node install
[ https://issues.apache.org/jira/browse/TRAFODION-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-1565. - Resolution: Fixed > Remove check for pdsh on single node install > > > Key: TRAFODION-1565 > URL: https://issues.apache.org/jira/browse/TRAFODION-1565 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Amanda Moran >Assignee: Amanda Moran >Priority: Minor > > pdsh can be installed on a single node and Trafodion will continue to work. > Check from the installer can be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1951) Unable to install trafodion due to java version mismatch
[
https://issues.apache.org/jira/browse/TRAFODION-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amanda Moran resolved TRAFODION-1951.
-
Resolution: Fixed
> Unable to install trafodion due to java version mismatch
>
>
> Key: TRAFODION-1951
> URL: https://issues.apache.org/jira/browse/TRAFODION-1951
> Project: Apache Trafodion
> Issue Type: Bug
> Components: installer
>Reporter: Roberta Marton
>Assignee: Amanda Moran
>
> After downloading the latest JAVA version today
> (java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el6_7.x86_64) trafodion installation
> (trafodion_install) is failing with the following error:
> ***ERROR: Your existing JAVA_HOME on is less than 1.7.0_65
> ***ERROR: Your Java Version on = java version "1.7.0_101"
> OpenJDK Runtime Environment (rhel-2.6.6.1.el6_7-x86_64 u101-b00)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> ***ERROR: Required java version on should be greater than 1.7.0_65
> It seems the check in traf_config_check is only looking at two bytes for the
> check and now the java version has gone to three bytes.
> To work around, I temporarily changed the following in traf_config_check file
> and my installation proceeded.
> if [[ "${THIS_JVM_VER:20:1}" -eq "0" ]] || [[ "${THIS_JVM_VER:20:2}" -lt
> $JAVA65 ]
> if [[ "${THIS_JVM_VER:20:2}" -eq "0" ]] || [[ "${THIS_JVM_VER:20:3}" -lt
> $JAVA65 ]
> Surrounding code:
> #Checking if using 1.7.0_n
> if [[ "${THIS_JVM_VER:18:1}" -eq "0" ]] && [[ "$temp_JAVA" -eq "$JAVA7" ]];
> then
> if [[ "${THIS_JVM_VER:20:1}" -eq "0" ]] || [[ "${THIS_JVM_VER:20:2}" -lt
> $JAVA65 ]]; then
> error="true"
> fi
> fi
> if [[ -n $error ]]; then
>errorFound=1
>echo "JAVA HOME" >> $ERROR_LOG
>echo "***ERROR: Your existing JAVA_HOME on $node is less than $REQ_VER"
> >> $ERROR_LOG
> echo "***ERROR: Your Java Version on $node = $THIS_JVM_VER" >> $ERROR_LOG
> echo "***ERROR: Required java version on $node should be greater than
> $REQ_VER" >> $ERROR_LOG
> fi
> fi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2123) JAVA_HOME check error when using OPEN-JDK
[ https://issues.apache.org/jira/browse/TRAFODION-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-2123. - Resolution: Fixed > JAVA_HOME check error when using OPEN-JDK > - > > Key: TRAFODION-2123 > URL: https://issues.apache.org/jira/browse/TRAFODION-2123 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Amanda Moran >Assignee: Amanda Moran >Priority: Minor > > When using open-jdk as java for JAVA_HOME installer will throw an error > during version checking but will not exit. > /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: > line 436: [[: ": syntax error: operand expected (error token is """) > /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: > line 441: [[: ": syntax error: operand expected (error token is """) > /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: > line 448: [[: .: syntax error: operand expected (error token is ".") > Install will continue and everything is fine (open jdk is fine to be used) > but the error looks scary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1908) Errors when creating Trafodion user id
[ https://issues.apache.org/jira/browse/TRAFODION-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-1908. - Resolution: Fixed > Errors when creating Trafodion user id > -- > > Key: TRAFODION-1908 > URL: https://issues.apache.org/jira/browse/TRAFODION-1908 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Amanda Moran >Assignee: Amanda Moran > > If there are errors during the creation of the trafodion user id, the > installer is not find the error and exiting. > The installer needs to find those errors and exit out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1470) Add Trafodion user id to hbase group
[ https://issues.apache.org/jira/browse/TRAFODION-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-1470. - Resolution: Fixed > Add Trafodion user id to hbase group > > > Key: TRAFODION-1470 > URL: https://issues.apache.org/jira/browse/TRAFODION-1470 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Amanda Moran >Assignee: Amanda Moran >Priority: Minor > > Add Trafodion user id to hbase group: > sudo usermod -a -G hbase trafodion > to make sure hbase is able to clean up properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-957) LP Bug: 1415227 - trafodion_install default directory should be related to current trafodion tar file
[ https://issues.apache.org/jira/browse/TRAFODION-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amanda Moran resolved TRAFODION-957. Resolution: Fixed > LP Bug: 1415227 - trafodion_install default directory should be related to > current trafodion tar file > - > > Key: TRAFODION-957 > URL: https://issues.apache.org/jira/browse/TRAFODION-957 > Project: Apache Trafodion > Issue Type: Bug > Components: installer >Reporter: Chris Tjepkema >Assignee: Amanda Moran >Priority: Minor > > Enter directory to install trafodion to, default is > '/opt/trafodion/trafodion-20141008_0830': > /opt/trafodion/trafodion-20150125_0830 > Above we have default from prior install but even though we entered a new tar > location > Enter location of trafodion tar file > (/root/Downloads/trafodion-20141008_0830.tar.gz): > /root/Downloads/trafodion-20150125_0830.tar.gz > the default install location is where the old install was and not related to > the new tar install file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2181) allow incompatible operations in sql queries
Anoop Sharma created TRAFODION-2181: --- Summary: allow incompatible operations in sql queries Key: TRAFODION-2181 URL: https://issues.apache.org/jira/browse/TRAFODION-2181 Project: Apache Trafodion Issue Type: Improvement Reporter: Anoop Sharma Assignee: Anoop Sharma Priority: Minor Many operations between incompatible datatypes are currently supported through special cqds or are not fully supported. For example: comparison between numeric and character (where 1 = '2'), or arithmetic operation between numeric and character ( 1 + '2'), etc. Areas where incompatible operations can happen are: -- assignment in insert and update statement. -- comparison predicates -- some conversions -- union or case statement -- arithmetic operations -- some string operations (like concat: 'a' || 2 ) This jira is to enable, externalize and support incompatible operations wherever possible. It may not be full support for all cases but could be further enhanced going forward. It will help in porting and running queries from other databases which support incompatible operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2166) UPDATE STATS ON NECESSARY COLUMNS does not work on Hive tables
[ https://issues.apache.org/jira/browse/TRAFODION-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Wayne Birdsall resolved TRAFODION-2166. - Resolution: Fixed Fix Version/s: 2.1-incubating > UPDATE STATS ON NECESSARY COLUMNS does not work on Hive tables > -- > > Key: TRAFODION-2166 > URL: https://issues.apache.org/jira/browse/TRAFODION-2166 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.1-incubating > Environment: All >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall > Fix For: 2.1-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2166) UPDATE STATS ON NECESSARY COLUMNS does not work on Hive tables
[ https://issues.apache.org/jira/browse/TRAFODION-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433606#comment-15433606 ] ASF GitHub Bot commented on TRAFODION-2166: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/668 > UPDATE STATS ON NECESSARY COLUMNS does not work on Hive tables > -- > > Key: TRAFODION-2166 > URL: https://issues.apache.org/jira/browse/TRAFODION-2166 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.1-incubating > Environment: All >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2180) Enable and add support for various non-ansi sql syntax and functionality
Anoop Sharma created TRAFODION-2180: --- Summary: Enable and add support for various non-ansi sql syntax and functionality Key: TRAFODION-2180 URL: https://issues.apache.org/jira/browse/TRAFODION-2180 Project: Apache Trafodion Issue Type: Improvement Reporter: Anoop Sharma Assignee: Anoop Sharma Priority: Minor There are many expression functions that are currently not fully supported, or are enabled only through special cqds. This jira is to externalize, enable and add that functionality. Some of those functions are GREATEST, MONTHS_BETWEEN, BYTEINT, etc. A complete list of functionality that should be enabled will be updated later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2174) sometime sqstop hang and cannot stop system
[ https://issues.apache.org/jira/browse/TRAFODION-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433459#comment-15433459 ] Amanda Moran commented on TRAFODION-2174: - +1 Thanks for starting to track this. > sometime sqstop hang and cannot stop system > --- > > Key: TRAFODION-2174 > URL: https://issues.apache.org/jira/browse/TRAFODION-2174 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > this issue occurred randomly, not very clear what is the consequence. People > use Ctrl+C and then ckillall, not sure if this is safe. > File jira to track it, next time meet this, we may need to gather more debug > info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2179) Memory leak from long running mxosrvr
hazi goldman created TRAFODION-2179:
---
Summary: Memory leak from long running mxosrvr
Key: TRAFODION-2179
URL: https://issues.apache.org/jira/browse/TRAFODION-2179
Project: Apache Trafodion
Issue Type: Bug
Components: sql-cmp
Affects Versions: any
Reporter: hazi goldman
Priority: Minor
Memory leak from long running mxosrvr related to pcode expression cache.
Adding this row to default table prevents issue.
insert into "_MD_".defaults values ('PCODE_EXPR_CACHE_ENABLED', '0',
'workaround for memory leak in mxosrvr') ;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-2178) TM Recovery exception in HRegionInfo.readFields
[ https://issues.apache.org/jira/browse/TRAFODION-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Subbiah updated TRAFODION-2178: -- Assignee: Sean Broeder > TM Recovery exception in HRegionInfo.readFields > --- > > Key: TRAFODION-2178 > URL: https://issues.apache.org/jira/browse/TRAFODION-2178 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm >Reporter: Sean Broeder >Assignee: Sean Broeder > > Unfortunately, the stack trace I had of the exception was on an AWS cluster > that has been reclaimed, so I cannot provide the stack trace, but the > exception was in HRegionInfo.readFields > Email from shangsheng - > I did check other logs files under jt01 (where TM0 died) and found some > exceptions been thrown from TM recovery thread due to > “HRegionInfo.readFields”. However, these troubled statements are NOT in R2.1. > I do a comparison between R2.1 and R2.2 (for HBaseTxClient.java) and there > are many changes (most of them are exception handling related). These > statements accidently show up in R2.2 code (probably get merged in from > Trafodion path). I assume JoshuaTree is based on R2.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2159) Unnest correlated subquery with explicit groupby
[ https://issues.apache.org/jira/browse/TRAFODION-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433136#comment-15433136 ] ASF GitHub Bot commented on TRAFODION-2159: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/657 > Unnest correlated subquery with explicit groupby > > > Key: TRAFODION-2159 > URL: https://issues.apache.org/jira/browse/TRAFODION-2159 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.0-incubating >Reporter: Suresh Subbiah >Assignee: Suresh Subbiah > Fix For: 2.1-incubating > > Attachments: GroupByUnnest.pdf > > > Correlated subqueries with the pattern shown on the left side of the > attachment are currently not unnested. When cqd subquery_unnesting is set to > 'DEBUG' this warning message is seen > *** WARNING[2997] (Subquery was not unnested. Reason: Right grandchild of > TSJ is a semijoin or a group by) > An example query is > prepare XX from > select t40.a > from t40 > where t40.b >= (select avg(counta) from (select count(a) as counta from t44 > where t40.c = t44.b group by t44.c)) ; > > Here the "group by t44.c" in the subquery prevents it from being unnested, > while "t40.c = t44.b" is the correlation predicate. > With the transformation shown in the right side of the attachment this query > will be unnested to this equivalent form, which has no explicit correlation > select a0 from > (select a0, avg(counta4) avga4 from > (select a0, b0, count(a4) counta4 from > (select t40.a a0, t40.b b0, t44.a a4, t44.c c4 from > t40,t44 > where t40.c = t44.b )T1(a0,b0,a4,c4) > group by (a0,b0,c4)) T2(a0,b0,counta4) > group by (a0,b0) > having b0 >= avga4) T3(a0, avga4) ; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2178) TM Recovery exception in HRegionInfo.readFields
Sean Broeder created TRAFODION-2178: --- Summary: TM Recovery exception in HRegionInfo.readFields Key: TRAFODION-2178 URL: https://issues.apache.org/jira/browse/TRAFODION-2178 Project: Apache Trafodion Issue Type: Bug Components: dtm Reporter: Sean Broeder Unfortunately, the stack trace I had of the exception was on an AWS cluster that has been reclaimed, so I cannot provide the stack trace, but the exception was in HRegionInfo.readFields Email from shangsheng - I did check other logs files under jt01 (where TM0 died) and found some exceptions been thrown from TM recovery thread due to “HRegionInfo.readFields”. However, these troubled statements are NOT in R2.1. I do a comparison between R2.1 and R2.2 (for HBaseTxClient.java) and there are many changes (most of them are exception handling related). These statements accidently show up in R2.2 code (probably get merged in from Trafodion path). I assume JoshuaTree is based on R2.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2177) Revoke combined column privileges from role failed
Gao, Rui-Xian created TRAFODION-2177: Summary: Revoke combined column privileges from role failed Key: TRAFODION-2177 URL: https://issues.apache.org/jira/browse/TRAFODION-2177 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Revoke combined column privileges from role failed, but revoke the privileges seperately would succeed. Reproduce Steps -- create role role1; create schema grantsch; set schema grantsch; create table a03tab1(col1 int, col2 int, col3 varchar(10))no partition; grant insert(col1,col2), select on a03tab1 to role1; SQL>revoke insert(col1,col2), select on a03tab1 from role1; *** ERROR[1037] Revoke failed because of a dependent grant between authorization ID _SYSTEM and authorization ID DB__ROOT [2016-08-17 10:00:20] >>revoke select on a03tab1 from role1; --- SQL operation complete. >>revoke insert(col1,col2) on a03tab1 from role1; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2176) a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself
Gao, Rui-Xian created TRAFODION-2176: Summary: a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself Key: TRAFODION-2176 URL: https://issues.apache.org/jira/browse/TRAFODION-2176 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Priority: Minor a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself. But the grant will succeed without the by clause. Reproduce Steps -- create role role1; create role role2; register component comp1; create component privilege created as 'cr' on comp1 ; create component privilege updated as 'up' on comp1 ; create component privilege deleted as 'de' on comp1 ; grant component privilege created ,updated on comp1 to qauser1 with grant option by db__root; connect as qauser1: SQL>grant component privilege updated on comp1 to qauser2 by qauser1; *** ERROR[1017] You are not authorized to perform this operation. [2016-08-16 08:31:00] SQL>grant component privilege updated on comp1 to qauser2; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2175) a user should only see specific schemas/tables that he has privileges to
Gao, Rui-Xian created TRAFODION-2175: Summary: a user should only see specific schemas/tables that he has privileges to Key: TRAFODION-2175 URL: https://issues.apache.org/jira/browse/TRAFODION-2175 Project: Apache Trafodion Issue Type: Improvement Components: sql-security Environment: OS -- centos6.7 , centos7.1 , centos7.2 esgynDB -- R2.2 daily build Reporter: Gao, Rui-Xian Assignee: Roberta Marton we have a requirement that a user should only see the objects that he has privileges to do operations on. Current feature is, ‘get schemas’ will return all schemas in the database, and in a private schema created by a user, another user can still see all tables with ‘get tables’, and also can check table’s structure with ‘showddl’. If we have many customer data on cloud cluster, we don’t want a customer to view any other customers’ data, we want the customers to be isolated from each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2174) sometime sqstop hang and cannot stop system
[ https://issues.apache.org/jira/browse/TRAFODION-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2174: --- Assignee: liu ming > sometime sqstop hang and cannot stop system > --- > > Key: TRAFODION-2174 > URL: https://issues.apache.org/jira/browse/TRAFODION-2174 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > this issue occurred randomly, not very clear what is the consequence. People > use Ctrl+C and then ckillall, not sure if this is safe. > File jira to track it, next time meet this, we may need to gather more debug > info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2174) sometime sqstop hang and cannot stop system
liu ming created TRAFODION-2174: --- Summary: sometime sqstop hang and cannot stop system Key: TRAFODION-2174 URL: https://issues.apache.org/jira/browse/TRAFODION-2174 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming this issue occurred randomly, not very clear what is the consequence. People use Ctrl+C and then ckillall, not sure if this is safe. File jira to track it, next time meet this, we may need to gather more debug info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2170) certain create table DDL will fail with core dump
[ https://issues.apache.org/jira/browse/TRAFODION-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2170 started by liu ming. --- > certain create table DDL will fail with core dump > - > > Key: TRAFODION-2170 > URL: https://issues.apache.org/jira/browse/TRAFODION-2170 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > create table test2170 ( > c1 varchar(255) CHARACTER SET UTF8 not null, > c2 varchar(256) CHARACTER SET UTF8 not null, > c3 varchar(256) CHARACTER SET UTF8 not null, > c4 int not null , > c5 int, > primary key(c1,c2,c3,c4)) > salt using 4 partitions ; > This will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2170) certain create table DDL will fail with core dump
[ https://issues.apache.org/jira/browse/TRAFODION-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432451#comment-15432451 ] liu ming commented on TRAFODION-2170: - DTM hardcode the key buffer to 2048. Need to either allocate dynamic buffer as required, or return error if the keyLength greater than 2048. > certain create table DDL will fail with core dump > - > > Key: TRAFODION-2170 > URL: https://issues.apache.org/jira/browse/TRAFODION-2170 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > create table test2170 ( > c1 varchar(255) CHARACTER SET UTF8 not null, > c2 varchar(256) CHARACTER SET UTF8 not null, > c3 varchar(256) CHARACTER SET UTF8 not null, > c4 int not null , > c5 int, > primary key(c1,c2,c3,c4)) > salt using 4 partitions ; > This will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
