[jira] [Resolved] (TRAFODION-2927) Keep log information for UPDATE STATISTICS in case of errors
[ https://issues.apache.org/jira/browse/TRAFODION-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Wayne Birdsall resolved TRAFODION-2927. - Resolution: Fixed Fix Version/s: 2.3 > Keep log information for UPDATE STATISTICS in case of errors > > > Key: TRAFODION-2927 > URL: https://issues.apache.org/jira/browse/TRAFODION-2927 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.3 >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall >Priority: Major > Fix For: 2.3 > > > Presently, UPDATE STATISTICS keeps a detailed log of its internal activities > if one has specifed "update statistics log on" in advance. > In production scenarios, this is typically not done. That means when a > long-running UPDATE STATISTICS command fails on a large table, one has to > redo it with logging turned on in order to troubleshoot. > A better practice might be to always log, and delete the log if the operation > succeeds. > Another issue with UPDATE STATISTICS logs is their location. The directory is > different than other Trafodion logs and is sometimes hard to find. As part of > this JIRA, consideration should be given to writing the logs to the Trafodion > logs directory instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TRAFODION-2927) Keep log information for UPDATE STATISTICS in case of errors
[ https://issues.apache.org/jira/browse/TRAFODION-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355758#comment-16355758 ] ASF GitHub Bot commented on TRAFODION-2927: --- Github user asfgit closed the pull request at: https://github.com/apache/trafodion/pull/1429 > Keep log information for UPDATE STATISTICS in case of errors > > > Key: TRAFODION-2927 > URL: https://issues.apache.org/jira/browse/TRAFODION-2927 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.3 >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall >Priority: Major > > Presently, UPDATE STATISTICS keeps a detailed log of its internal activities > if one has specifed "update statistics log on" in advance. > In production scenarios, this is typically not done. That means when a > long-running UPDATE STATISTICS command fails on a large table, one has to > redo it with logging turned on in order to troubleshoot. > A better practice might be to always log, and delete the log if the operation > succeeds. > Another issue with UPDATE STATISTICS logs is their location. The directory is > different than other Trafodion logs and is sometimes hard to find. As part of > this JIRA, consideration should be given to writing the logs to the Trafodion > logs directory instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TRAFODION-2772) retrieve a value from Json string got an error: Json value is invalid
[
https://issues.apache.org/jira/browse/TRAFODION-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355770#comment-16355770
]
ASF GitHub Bot commented on TRAFODION-2772:
---
Github user asfgit closed the pull request at:
https://github.com/apache/trafodion/pull/1439
> retrieve a value from Json string got an error: Json value is invalid
> -
>
> Key: TRAFODION-2772
> URL: https://issues.apache.org/jira/browse/TRAFODION-2772
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Yang, Yongfeng
>Assignee: Yang, Yongfeng
>Priority: Major
>
> >>create table json(str varchar(200));
> >>select json_object_field_text('{"f2":1}', 'f2') from json;
> *** ERROR[8971] JSON value is invalid.
> --- 0 row(s) selected.
> >>
> the expected result should like below.
> >>select json_object_field_text('{"f2":1}', 'f2') from (values(1)) T;
> (EXPR)
>
> 1
> --- 1 row(s) selected.
> >>
> >>select json_object_field_text('{"f2":1}', 'f2') from (values(1)) T;
> (EXPR)
>
> 1
> --- 1 row(s) selected.
> >>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TRAFODION-2955) odb crash when executing sql statements in a file and the file contains space only line.
[ https://issues.apache.org/jira/browse/TRAFODION-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355788#comment-16355788 ] ASF GitHub Bot commented on TRAFODION-2955: --- Github user asfgit closed the pull request at: https://github.com/apache/trafodion/pull/1442 > odb crash when executing sql statements in a file and the file contains space > only line. > - > > Key: TRAFODION-2955 > URL: https://issues.apache.org/jira/browse/TRAFODION-2955 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-odb >Reporter: 苏锦佩 >Assignee: 苏锦佩 >Priority: Major > > 1. create a sql file: > vi temp.sql > 1 drop table odb_copy_customer1;$ > 2 create table odb_copy_customer1(id int, name varchar(32));$ > 3 insert into odb_copy_customer1 values (1, 'hadoop');$ > 4 $ > 5 insert into odb_copy_customer1 values (2, 'hive'); $ > 2. ./odb64luo -u odb -p odb -d oracle -f temp.sql > 3. [0.0.2]--- 1 row(s) inserted in 0.021s (prep 0.000s, exec 0.021s, fetch > 0.000s/0.000s) > Segmentation fault -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TRAFODION-2927) Keep log information for UPDATE STATISTICS in case of errors
[ https://issues.apache.org/jira/browse/TRAFODION-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355899#comment-16355899 ] David Wayne Birdsall commented on TRAFODION-2927: - Note: I changed the default for CQD USTAT_AUTOMATIC_LOGGING to 'ON' after measuring the overhead of logging. In my measurements, it amounted to about 0.32 seconds on average per UPDATE STATISTICS command. That is in the realm of noise for UPDATE STATISTICS. So it seems best to have it 'ON' always. > Keep log information for UPDATE STATISTICS in case of errors > > > Key: TRAFODION-2927 > URL: https://issues.apache.org/jira/browse/TRAFODION-2927 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.3 >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall >Priority: Major > > Presently, UPDATE STATISTICS keeps a detailed log of its internal activities > if one has specifed "update statistics log on" in advance. > In production scenarios, this is typically not done. That means when a > long-running UPDATE STATISTICS command fails on a large table, one has to > redo it with logging turned on in order to troubleshoot. > A better practice might be to always log, and delete the log if the operation > succeeds. > Another issue with UPDATE STATISTICS logs is their location. The directory is > different than other Trafodion logs and is sometimes hard to find. As part of > this JIRA, consideration should be given to writing the logs to the Trafodion > logs directory instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TRAFODION-2874) LOB: Add syntax to return filename of a LOB data file for external LOBs.
[
https://issues.apache.org/jira/browse/TRAFODION-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355891#comment-16355891
]
ASF GitHub Bot commented on TRAFODION-2874:
---
Github user sandhyasun commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1428#discussion_r166720182
--- Diff: core/sql/exp/ExpLOBaccess.cpp ---
@@ -870,6 +870,67 @@ Ex_Lob_Error ExLob::getLength(char *handleIn, Int32
handleInLen,Int64
}
return err;
}
+Ex_Lob_Error ExLob::getOffset(char *handleIn, Int32 handleInLen,Int64
,LobsSubOper so, Int64 transId)
+{
+ char logBuf[4096];
+ Int32 cliErr = 0;
+ Ex_Lob_Error err=LOB_OPER_OK;
+ char *blackBox = new(getLobGlobalHeap()) char[MAX_LOB_FILE_NAME_LEN+6];
+ Int32 blackBoxLen = 0;
+ Int64 dummy = 0;
+ Int32 dummy2 = 0;
+ if (so != Lob_External_File)
+{
+
+ cliErr = SQL_EXEC_LOBcliInterface(handleIn,
handleInLen,NULL,NULL,NULL,NULL,LOB_CLI_SELECT_LOBOFFSET,LOB_CLI_ExecImmed,,0,
0, 0,0,transId,lobTrace_);
+
+ if (cliErr < 0 ) {
+str_sprintf(logBuf,"CLI SELECT_LOBOFFSET returned error
%d",cliErr);
+lobDebugInfo(logBuf, 0,__LINE__,lobTrace_);
+
+return LOB_DESC_READ_ERROR;
+ }
+}
+
+ return err;
+}
+
+Ex_Lob_Error ExLob::getFileName(char *handleIn, Int32 handleInLen, char
*outFileName, Int32 , LobsSubOper so, Int64 transId)
+{
+ char logBuf[4096];
+ Int32 cliErr = 0;
+ Ex_Lob_Error err=LOB_OPER_OK;
+ Int64 dummy = 0;
+ Int32 dummy2 = 0;
+ if (so != Lob_External_File)
+{
+ //Derive the filename from the LOB handle and return
+ str_cpy_all(outFileName, (char
*)lobDataFile_.data(),lobDataFile_.length());
--- End diff --
Internally we allocate enough to hold the name. But when the final result
is copied out, it's copied out to a caller provided address (64 bit address).
So we are assuming the caller (mxosrvr) has allocated enough space.
> LOB: Add syntax to return filename of a LOB data file for external LOBs.
> -
>
> Key: TRAFODION-2874
> URL: https://issues.apache.org/jira/browse/TRAFODION-2874
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
>Affects Versions: 2.3
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
>Priority: Major
>
> For external LOBs, Trafodion does not save the LOB data in it's internal
> trafodion namespace. It saves only the LOB handle information and the actual
> LOB data remains outside in users namespace in HDFS.So inserts are very
> eifficient. During extract from an external LOB today, we extract the LOB
> data from the external file and return it to the user. Need to extend the
> Extract syntax to also be able to return the external LOB data filename alone
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TRAFODION-2899) Catalog API SQLColumns does not support ODBC2.x
[ https://issues.apache.org/jira/browse/TRAFODION-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356270#comment-16356270 ] ASF GitHub Bot commented on TRAFODION-2899: --- Github user asfgit closed the pull request at: https://github.com/apache/trafodion/pull/1386 > Catalog API SQLColumns does not support ODBC2.x > --- > > Key: TRAFODION-2899 > URL: https://issues.apache.org/jira/browse/TRAFODION-2899 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-mxosrvr >Affects Versions: any > Environment: Centos 6.7 >Reporter: XuWeixin >Assignee: XuWeixin >Priority: Major > Fix For: 2.2-incubating > > > When using ODBC2.x to get description of columns, failure occurs but no error > returns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TRAFODION-2957) T4JDBC should support compound statement
liu ming created TRAFODION-2957: --- Summary: T4JDBC should support compound statement Key: TRAFODION-2957 URL: https://issues.apache.org/jira/browse/TRAFODION-2957 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming Assignee: liu ming should be able to run multiple statements in one JDBC call. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TRAFODION-2335) support functions in the column default definition
[ https://issues.apache.org/jira/browse/TRAFODION-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355373#comment-16355373 ] liu ming commented on TRAFODION-2335: - * 当前日期作为默认值： create table t1(c varchar(10) default to_char(sysdate,'MMDD')); * 使用sequence作为默认值： ## create sequence test_seq; ## create table sequence_test_tab(c number default test_seq.nextval); > support functions in the column default definition > -- > > Key: TRAFODION-2335 > URL: https://issues.apache.org/jira/browse/TRAFODION-2335 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming >Priority: Minor > > It is possible to use Function in create table DDL for column default in some > other RDBMS, it is desired to support that as well. > Requirement is still not 100% clear, need further study. > File JIRA to track first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
