[jira] [Commented] (TRAFODION-2483) Trafodion treat '\' as NULL in hive table

[ASF GitHub Bot (JIRA)]

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

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

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


https://github.com/apache/incubator-trafodion/pull/1055#discussion_r110909382
  
--- Diff: core/sql/executor/ExHdfsScan.cpp ---
@@ -1653,7 +1653,7 @@ char * 
ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow(int ,
   // for non-varchar, length of zero indicates a null 
value.
   // For all datatypes, HIVE_DEFAULT_NULL_STRING('\N') 
indicates a null value.
   if (((len == 0) && (tgtAttr && (NOT 
DFS2REC::isSQLVarChar(tgtAttr->getDatatype() ||
-  ((len > 0) && (memcmp(sourceData, 
HIVE_DEFAULT_NULL_STRING, len) == 0)))
+  ((len == strlen(HIVE_DEFAULT_NULL_STRING)) && 
(memcmp(sourceData, HIVE_DEFAULT_NULL_STRING, len) == 0)))
--- End diff --

I am not sure if the c++ compiler would optimize this. You could improve 
this further by getting the strlen only once in the TCB


> Trafodion treat '\' as NULL in hive table
> -
>
> Key: TRAFODION-2483
> URL: https://issues.apache.org/jira/browse/TRAFODION-2483
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: Yang, Yongfeng
>
> If the source data in a hive table have '\', it will be mistakenly treated as 
> NULL value ('\N').
> Not correct string comparing inside 
> ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2569) Improve handling of index hints

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Improve handling of index hints
> ---
>
> Key: TRAFODION-2569
> URL: https://issues.apache.org/jira/browse/TRAFODION-2569
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.2-incubating
>
>
> We allow index hints of this form:
> select ... from table1 <<+index TRAFODION.SCH.IX1>> ...
> In many cases, the compiler does not choose the index specified in the hint, 
> however. A few improvements I am planning to do, if I can pull it off:
> * if we need an index join, make sure we get it using this index
> * allow hints in update statements
> * bind the names in the hint, so they don't have to be specified as 
> upper-case 3-part names.
> * issue a warning if the table name in the index does not specify an index



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2579) installers should allow multiple ldap hosts and ldap UID lines

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> installers should allow multiple ldap hosts and ldap UID lines
> --
>
> Key: TRAFODION-2579
> URL: https://issues.apache.org/jira/browse/TRAFODION-2579
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.2-incubating
>Reporter: Steve Varnau
>
> Both python and ambari installer seem to limit LDAP configuration.
> Instead of 
>LDAPHostName: host,host2
> the generated config should be:
>LDAPHostName: host
>LDAPHostName: host2
> The same is true of the UniqueIdentifier keyword.  These should be one per 
> line and an identifier string can contain embedded spaces. A better separator 
> would perhaps be semi-colon.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2586) UPSERT USING LOAD running slower than UPSERT with transactions disabled

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> UPSERT USING LOAD running slower than UPSERT with transactions disabled
> ---
>
> Key: TRAFODION-2586
> URL: https://issues.apache.org/jira/browse/TRAFODION-2586
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: any
>Reporter: Suresh Subbiah
>Assignee: Suresh Subbiah
> Fix For: 2.2-incubating
>
>
> Tricke loading with UPSERT USING LOAD was observed to be slower than trickle 
> load with UPSERT and transactions disabled. For a table with no indexes the 
> two runs should have performed equivalently.
> This can be observed with ODB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (TRAFODION-2512) index access with MDAM not chosen where predicate is range spec

[Suresh Subbiah (JIRA)]

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

Suresh Subbiah closed TRAFODION-2512.
-
Resolution: Fixed

> index access with MDAM not chosen where predicate is range spec
> ---
>
> Key: TRAFODION-2512
> URL: https://issues.apache.org/jira/browse/TRAFODION-2512
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.2-incubating
>Reporter: Eric Owhadi
>Assignee: Suresh Subbiah
>
> create table tbl (
> k1 int not null,
> k2 int not null,
> ts timestamp not null,
> a char(10),
> b varchar(30),
> c largeint,
> primary key (k1,k2,ts))
> salt using 8 partitions 
> division by (date_trunc('MONTH', ts)) ;
> upsert using load into tbl
> select num/1000, num, DATEADD(SECOND,-num,CURRENT_TIMESTAMP),cast(num as 
> char(10)), cast(num as varchar(30)), num*1000
> from (select 
> 1000*x1000+100*x100+10*x10+1*x1+1000*x1000+100*x100+10*x10+x1
>  as num
>   from (values (0)) seed(c)
>   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 x10
>   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 x1000
>   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 x10
>   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 x1000  
>   ) T
> ;
> create index tbl_idx_b on tbl(b) salt like table;
> update statistics for table tbl on every column sample;
> prepare s from select k1 where b = '1234567';
> prepare ss from select k1 from b like '1234567%';
> see how s is correctly picking index access.
> see how ss, regardless of th elike correctly been transform into a range 
> spec, end up doing a full main table scan instead of going after the index on 
> b using MDAM and the range spec inside the mdam disjunct.
> SQL>prepare s from select k1 from tbl where b = '1234567';
> --- SQL command prepared.
> SQL>explain options 'f' s;
>  
> LC   RC   OP   OPERATOR  OPT   DESCRIPTION   CARD   
>          -
>  
> 1.2root  1.00E+000
> ..1trafodion_index_scanIDX_TBL_B 1.00E+000
> --- SQL operation complete.
> SQL>explain s;
>  
> -- PLAN 
> SUMMARY
> MODULE_NAME .. DYNAMICALLY COMPILED
> STATEMENT_NAME ... S
> PLAN_ID .. 212355075543213868
> ROWS_OUT . 1
> EST_TOTAL_COST ... 0.15
> STATEMENT  select k1 from tbl where b = '1234567'
>  
>  
> -- NODE 
> LISTING
> ROOT ==  SEQ_NO 2ONLY CHILD 1
> REQUESTS_IN .. 1
> ROWS_OUT . 1
> EST_OPER_COST  0
> EST_TOTAL_COST ... 0.15
> DESCRIPTION
>   max_card_est ... 1
>   fragment_id  0
>   parent_frag  (none)
>   fragment_type .. master
>   statement_index  0
>   affinity_value . 0
>   max_max_cardinality  1
>   total_overflow_size  0.00 KB
>   xn_access_mode . read_only
>   xn_autoabort_interval0
>   auto_query_retry ... enabled
>   plan_version ... 2,600
>   embedded_arkcmp  used
>   ObjectUIDs . 636255280475776270
>   select_list  TRAFODION.ERIC.IDX_TBL_B.K1
>   input_variables  %('1234567')
>  
>  
> TRAFODION_INDEX_SCAN ==  SEQ_NO 1NO CHILDREN
> TABLE_NAME ... TBL
> REQUESTS_IN .. 1
> ROWS_OUT . 1
> EST_OPER_COST  0.15
> EST_TOTAL_COST ... 0.15
> DESCRIPTION
>   max_card_est ... 1
>   fragment_id  0
>   parent_frag  (none)
>   fragment_type .. master
>   scan_type .. subset scan limited by mdam of index
>  TRAFODION.ERIC.IDX_TBL_B(TRAFODION.ERIC.TBL)
>   object_type  Trafodion
>   cache_size ... 100
>   probes . 1
>   rows_accessed .. 1
>   column_retrieved ... #1:1
>   key_columns  TRAFODION.ERIC.IDX_TBL_B._SALT_,
>  TRAFODION.ERIC.IDX_TBL_B.B,
>  TRAFODION.ERIC.IDX_TBL_B._DIVISION_1_,
>  TRAFODION.ERIC.IDX_TBL_B.K1,
>  TRAFODION.ERIC.IDX_TBL_B.K2,
>  TRAFODION.ERIC.IDX_TBL_B.TS
>   mdam_disjunct .. (TRAFODION.ERIC.IDX_TBL_B.B = %('1234567'))
> --- 

[jira] [Resolved] (TRAFODION-2569) Improve handling of index hints

[Hans Zeller (JIRA)]

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

Hans Zeller resolved TRAFODION-2569.

Resolution: Fixed

> Improve handling of index hints
> ---
>
> Key: TRAFODION-2569
> URL: https://issues.apache.org/jira/browse/TRAFODION-2569
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.2-incubating
>
>
> We allow index hints of this form:
> select ... from table1 <<+index TRAFODION.SCH.IX1>> ...
> In many cases, the compiler does not choose the index specified in the hint, 
> however. A few improvements I am planning to do, if I can pull it off:
> * if we need an index join, make sure we get it using this index
> * allow hints in update statements
> * bind the names in the hint, so they don't have to be specified as 
> upper-case 3-part names.
> * issue a warning if the table name in the index does not specify an index



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (TRAFODION-2569) Improve handling of index hints

[Hans Zeller (JIRA)]

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

Hans Zeller closed TRAFODION-2569.
--

> Improve handling of index hints
> ---
>
> Key: TRAFODION-2569
> URL: https://issues.apache.org/jira/browse/TRAFODION-2569
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.2-incubating
>
>
> We allow index hints of this form:
> select ... from table1 <<+index TRAFODION.SCH.IX1>> ...
> In many cases, the compiler does not choose the index specified in the hint, 
> however. A few improvements I am planning to do, if I can pull it off:
> * if we need an index join, make sure we get it using this index
> * allow hints in update statements
> * bind the names in the hint, so they don't have to be specified as 
> upper-case 3-part names.
> * issue a warning if the table name in the index does not specify an index



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2420) RMS enhancements

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> RMS enhancements
> 
>
> Key: TRAFODION-2420
> URL: https://issues.apache.org/jira/browse/TRAFODION-2420
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-general
>Affects Versions: 2.1-incubating
>Reporter: Selvaganesan Govindarajan
>Assignee: Selvaganesan Govindarajan
>
> Improve RMS to provide the following features/capabilities:
> 1. Currently RMS can list queries that consumed cpu time between two time 
> points. However, the calls to storage engine like hbase, hdfs etc are 
> blocking and these blocked APIs will not allow the Trafodion SQL engine 
> scheduler to detect the cpu time spent during the time the call was blocked. 
> Introduce a feature called SE offender (storage engine offender) to list the 
> queries that are blocked in storage engine more than a certain duration.
> 2. Remove counters that are no longer updated or needed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TRAFODION-2579) installers should allow multiple ldap hosts and ldap UID lines

[Steve Varnau (JIRA)]

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

Steve Varnau resolved TRAFODION-2579.
-
   Resolution: Fixed
Fix Version/s: 2.2-incubating

> installers should allow multiple ldap hosts and ldap UID lines
> --
>
> Key: TRAFODION-2579
> URL: https://issues.apache.org/jira/browse/TRAFODION-2579
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.2-incubating
>Reporter: Steve Varnau
> Fix For: 2.2-incubating
>
>
> Both python and ambari installer seem to limit LDAP configuration.
> Instead of 
>LDAPHostName: host,host2
> the generated config should be:
>LDAPHostName: host
>LDAPHostName: host2
> The same is true of the UniqueIdentifier keyword.  These should be one per 
> line and an identifier string can contain embedded spaces. A better separator 
> would perhaps be semi-colon.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TRAFODION-2586) UPSERT USING LOAD running slower than UPSERT with transactions disabled

[Suresh Subbiah (JIRA)]

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

Suresh Subbiah resolved TRAFODION-2586.
---
Resolution: Fixed

> UPSERT USING LOAD running slower than UPSERT with transactions disabled
> ---
>
> Key: TRAFODION-2586
> URL: https://issues.apache.org/jira/browse/TRAFODION-2586
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: any
>Reporter: Suresh Subbiah
>Assignee: Suresh Subbiah
> Fix For: 2.2-incubating
>
>
> Tricke loading with UPSERT USING LOAD was observed to be slower than trickle 
> load with UPSERT and transactions disabled. For a table with no indexes the 
> two runs should have performed equivalently.
> This can be observed with ODB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2516) Enhance stringtolob builtin function to take varchar/char columns as parameter

[ASF GitHub Bot (JIRA)]

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

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

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


https://github.com/apache/incubator-trafodion/pull/1041#discussion_r111035970
  
--- Diff: core/sql/bin/clitest.cpp ---
@@ -316,7 +317,9 @@ case 7:
  return retcode;
   }
 cout << "LOB handle for "<< columnname << ": " << lobHandle << 
endl;
-   retcode = updateAppendBufferToLobHandle(cliGlob,lobHandle);
+char *source= new char[300];
--- End diff --

This is a test program so I suppose we don't care about the memory leak 
here?


> Enhance stringtolob builtin function to take varchar/char columns as parameter
> --
>
> Key: TRAFODION-2516
> URL: https://issues.apache.org/jira/browse/TRAFODION-2516
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
>
> Today the stringtolob built in function that converts a string to a LOB type 
> before inserrting into a lob column takes a string literal as input. Need to 
> enhance it to take a char column or a varchar column as input too. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TRAFODION-2587) ip showed in dcsMaster monitor is not correct

[mashengchen (JIRA)]

mashengchen created TRAFODION-2587:
--

 Summary: ip showed in dcsMaster monitor is not correct
 Key: TRAFODION-2587
 URL: https://issues.apache.org/jira/browse/TRAFODION-2587
 Project: Apache Trafodion
  Issue Type: Bug
  Components: dcs
Reporter: mashengchen
Assignee: mashengchen


if client has two+ ip(use wifi or openvpn), then there may has a random ip send 
to dcsmaster, and thus, the mapping will not work correct, because dcsmaster 
use the socket ip
another case is if no mapping ip limit, once connect success, in dcsMaster 
monitor page there may show error ip

eg: 
client have two ip , 192.168.3.14 & 192.168.6.10
mapping ip criteria is 192.168.3.*
in this case client send 192.168.6.10, but the really ip which can connect to 
dcs side is 192.168.3.14, so the mapping will be error

client have two ip , 192.168.3.14 & 192.168.6.10
mapping ip criteria is no limit
in this case client send 192.168.6.10, but the really ip which can connect to 
dcs side is 192.168.3.14, then in dcsmaster monitor will show connected side is 
192.168.6.10



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TRAFODION-2588) monitor failed to start if part of zookeeper server is down

[Eason Zhang (JIRA)]

Eason Zhang created TRAFODION-2588:
--

 Summary: monitor failed to start if part of zookeeper server is 
down
 Key: TRAFODION-2588
 URL: https://issues.apache.org/jira/browse/TRAFODION-2588
 Project: Apache Trafodion
  Issue Type: Bug
  Components: foundation
Reporter: Eason Zhang
Assignee: Eason Zhang


monitor gets zookpper node list from env $ZOOKEEPER_NODES. If one of the 
zookeeper server in this node list is down, monitor will not start with 
'ZCONNECTIONLOSS' error:

2017-04-11 17:15:49,351, ERROR, ZOO, Node Number: 4294967295,, PIN: 21106 , 
Process Name: zooclient,,, TID: 21106, Message ID: 101370401, 
[CZClient::MakeClusterZNodes], zoo_exists() failed with error ZCONNECTIONLOSS

That is because zookeeper c client randomly picks up a zk server to connect 
with based on its own node selection algorithm. So the simple solution for 
monitor is that we do a retry when connection failed, let zookeeper c client to 
pick up another server from the list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2493) to_char with format 'MONTH DD, YYYY, HH:MI' is wrong

[ASF GitHub Bot (JIRA)]

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

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

Github user andyyangcn closed the pull request at:

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


> to_char with format 'MONTH DD, , HH:MI' is wrong
> 
>
> Key: TRAFODION-2493
> URL: https://issues.apache.org/jira/browse/TRAFODION-2493
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dev-environment
>Affects Versions: 2.0-incubating
>Reporter: Yuan Liu
>Assignee: Yang, Yongfeng
>
> SQL>select to_char(current_timestamp, 'MONTH DD, , HH:MI') from 
> (values(1));
> (EXPR)
> -
> February 21, 2017, 17:29:
> --- 1 row(s) selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2493) to_char with format 'MONTH DD, YYYY, HH:MI' is wrong

[ASF GitHub Bot (JIRA)]

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

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

GitHub user andyyangcn opened a pull request:

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

[TRAFODION-2493] to_char with format 'MONTH DD, , HH:MI' is wrong



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

$ git pull https://github.com/andyyangcn/incubator-trafodion bugfix2

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

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


commit 82052c2e804ab3a7c97011a145e90adb97216df1
Author: Andy Yang 
Date:   2017-04-11T09:35:53Z

[TRAFODION-2493] to_char with format 'MONTH DD, , HH:MI' is wrong




> to_char with format 'MONTH DD, , HH:MI' is wrong
> 
>
> Key: TRAFODION-2493
> URL: https://issues.apache.org/jira/browse/TRAFODION-2493
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dev-environment
>Affects Versions: 2.0-incubating
>Reporter: Yuan Liu
>Assignee: Yang, Yongfeng
>
> SQL>select to_char(current_timestamp, 'MONTH DD, , HH:MI') from 
> (values(1));
> (EXPR)
> -
> February 21, 2017, 17:29:
> --- 1 row(s) selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TRAFODION-2589) pyinstaller - do remote node initialize in parallel

[Eason Zhang (JIRA)]

Eason Zhang created TRAFODION-2589:
--

 Summary: pyinstaller - do remote node initialize in parallel
 Key: TRAFODION-2589
 URL: https://issues.apache.org/jira/browse/TRAFODION-2589
 Project: Apache Trafodion
  Issue Type: Bug
  Components: installer
Reporter: Eason Zhang
Assignee: Eason Zhang


Currently the remote node initialize work is done by a for loop, this is not 
efficient. Using threads to improve performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2589) pyinstaller - do remote node initialize in parallel

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mkby opened a pull request:

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

[TRAFODION-2589] pyinstaller - do remote node initialize in parallel



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

$ git pull https://github.com/mkby/incubator-trafodion 2589

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

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


commit f45c3aa6a541445142bddca9d18bf93d78458d40
Author: Eason 
Date:   2017-04-11T10:11:48Z

[TRAFODION-2589] pyinstaller - do remote node initialize in parallel




> pyinstaller - do remote node initialize in parallel
> ---
>
> Key: TRAFODION-2589
> URL: https://issues.apache.org/jira/browse/TRAFODION-2589
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> Currently the remote node initialize work is done by a for loop, this is not 
> efficient. Using threads to improve performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (TRAFODION-2587) ip showed in dcsMaster monitor is not correct

[mashengchen (JIRA)]

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

mashengchen closed TRAFODION-2587.
--
Resolution: Fixed

trafodion does not have mapping function

> ip showed in dcsMaster monitor is not correct
> -
>
> Key: TRAFODION-2587
> URL: https://issues.apache.org/jira/browse/TRAFODION-2587
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dcs
>Reporter: mashengchen
>Assignee: mashengchen
>
> if client has two+ ip(use wifi or openvpn), then there may has a random ip 
> send to dcsmaster, and thus, the mapping will not work correct, because 
> dcsmaster use the socket ip
> another case is if no mapping ip limit, once connect success, in dcsMaster 
> monitor page there may show error ip
> eg: 
> client have two ip , 192.168.3.14 & 192.168.6.10
> mapping ip criteria is 192.168.3.*
> in this case client send 192.168.6.10, but the really ip which can connect to 
> dcs side is 192.168.3.14, so the mapping will be error
> client have two ip , 192.168.3.14 & 192.168.6.10
> mapping ip criteria is no limit
> in this case client send 192.168.6.10, but the really ip which can connect to 
> dcs side is 192.168.3.14, then in dcsmaster monitor will show connected side 
> is 192.168.6.10



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TRAFODION-2483) Trafodion treat '\' as NULL in hive table

[ASF GitHub Bot (JIRA)]

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

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

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


https://github.com/apache/incubator-trafodion/pull/1055#discussion_r110865889
  
--- Diff: core/sql/executor/ExHdfsScan.cpp ---
@@ -1653,7 +1653,7 @@ char * 
ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow(int ,
   // for non-varchar, length of zero indicates a null 
value.
   // For all datatypes, HIVE_DEFAULT_NULL_STRING('\N') 
indicates a null value.
   if (((len == 0) && (tgtAttr && (NOT 
DFS2REC::isSQLVarChar(tgtAttr->getDatatype() ||
-  ((len > 0) && (memcmp(sourceData, 
HIVE_DEFAULT_NULL_STRING, len) == 0)))
+  ((len > 1) && (memcmp(sourceData, 
HIVE_DEFAULT_NULL_STRING, len) == 0)))
--- End diff --

For the current fix \NAA will not be treated as NULL. and I agree that 
making sure the length is equal is better.



> Trafodion treat '\' as NULL in hive table
> -
>
> Key: TRAFODION-2483
> URL: https://issues.apache.org/jira/browse/TRAFODION-2483
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: Yang, Yongfeng
>
> If the source data in a hive table have '\', it will be mistakenly treated as 
> NULL value ('\N').
> Not correct string comparing inside 
> ExHdfsScanTcb::extractAndTransformAsciiSourceToSqlRow



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)