[jira] [Resolved] (TRAFODION-1627) 'sqgen' cannot copy files to all nodes.
[
https://issues.apache.org/jira/browse/TRAFODION-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eason Zhang resolved TRAFODION-1627.
Resolution: Fixed
> 'sqgen' cannot copy files to all nodes.
> ---
>
> Key: TRAFODION-1627
> URL: https://issues.apache.org/jira/browse/TRAFODION-1627
> Project: Apache Trafodion
> Issue Type: Bug
> Components: foundation
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> 'shell.env', 'mon.env' doesn't exist on Trafodion, but 'sqgen' tries to use
> 'pdcp' command to copy them to all nodes:
>$PDCP -w ${ExNodeList[@]} -x `uname -n` sqconfig sqshell gomon.cold
> gomon.warm shell.env mon.env $PWD
> So this 'pdcp' command will fail to execute, all files will not be copied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1706) trafodion is not compatible with hbase 1.0 and later version
[ https://issues.apache.org/jira/browse/TRAFODION-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182831#comment-15182831 ] ASF GitHub Bot commented on TRAFODION-1706: --- GitHub user mashengchen opened a pull request: https://github.com/apache/incubator-trafodion/pull/367 TRAFODION-1706 support vanilla hbase1.0 & cdh 1.0.0-cdh5.4.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/mashengchen/incubator-trafodion master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/367.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 #367 commit 4ed6be8ceabeb10418ee7101081fe6fd1c02a12c Author: mashengchen Date: 2016-02-25T03:33:39Z TRAFODION-1706 commit 451df06d92f46bdf1fda61c080df05c272a5b56d Author: mashengchen Date: 2016-02-25T06:14:06Z Update Makefile commit d5a4882287a25e0f73674fe6029c503c601a6a58 Author: mashengchen Date: 2016-02-25T06:32:16Z remove some echo commit f547a6095b9d8c157a0273a9e9605b386fa6f440 Author: mashengchen Date: 2016-02-25T07:03:02Z update install_local_hadoop commit 2a842bcf3eea4984ed20cfef8f6d77c7a81d00ea Author: mashengchen Date: 2016-02-29T03:04:16Z update hbase_utilities & add hdp support commit de178c92734d136fbb683e6526d6015fd5ef00bf Author: mashengchen Date: 2016-03-01T01:40:38Z Update pp.awk add copyright commit e314529be30cc773840d4d03b76050158301e3ec Author: mashengchen Date: 2016-03-01T01:41:02Z Update reinstate_orig add copyright commit 2155c3dd1d9d48ddfb3cd86ec28dafcb4d3f3233 Author: mashengchen Date: 2016-03-01T01:41:32Z Update uncomment_string add copyright commit 78abccb045df63cc502cd2eab5bc13b1718d94e5 Author: mashengchen Date: 2016-03-01T01:41:52Z Update reinstate_orig commit 4c9cfe45ab55e42d6e5df6d2b429e493476692bf Author: mashengchen Date: 2016-03-01T01:46:40Z add copyright commit e7b1691013976b0c57b51a20496e9adc1bc7d5e8 Author: mashengchen Date: 2016-03-01T03:12:30Z add .tmpl file to .gitignore commit 28460bd8e3c86c934617fcebf1ed1594f7543847 Author: mashengchen Date: 2016-03-02T02:46:34Z add version info & remove unnecessory file commit 73c164b78d682aae95a2132f62d97385b5e27b08 Author: mashengchen Date: 2016-03-04T03:05:31Z remove duplicate copyright & roll back some change commit f1c7f3a7a896031fe37c261d26af52bd8eda611c Author: mashengchen Date: 2016-03-06T07:34:45Z update commit 71f80f6e7e6f4c8364cabaa0817e983ba695156e Author: mashengchen Date: 2016-03-07T09:52:34Z remove support hdp2_3 > trafodion is not compatible with hbase 1.0 and later version > > > Key: TRAFODION-1706 > URL: https://issues.apache.org/jira/browse/TRAFODION-1706 > Project: Apache Trafodion > Issue Type: Bug >Reporter: mashengchen >Assignee: mashengchen > > trafodion is not compatible with hbase 1.0 and later version.Some api is > changed, like Hlog was changed to WAL... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1848) LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr process
[
https://issues.apache.org/jira/browse/TRAFODION-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183323#comment-15183323
]
ASF GitHub Bot commented on TRAFODION-1848:
---
Github user arvind-narain commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/363#discussion_r55239271
--- Diff: core/sql/cli/Cli.cpp ---
@@ -9671,7 +9622,12 @@ Lng32 SQLCLI_LOBcliInterface
if (cliRC < 0)
{
cliInterface->retrieveSQLDiagnostics(myDiags);
-
+cliInterface->retrieveSQLDiagnostics(myDiags);
--- End diff --
This got duplicated - could be removed.
> LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr
> process
> --
>
> Key: TRAFODION-1848
> URL: https://issues.apache.org/jira/browse/TRAFODION-1848
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-exe
>Affects Versions: any
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
> Fix For: 2.0-incubating
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Need support to compact lob data files after a certain threshold is reached .
> Deleting or updating a table with lob columns cn cause the lob datafiles to
> be left with unused holes. These need to be compacted regularly.
> TO simplify the flow of execution, the mxlobsrvr process functionality is
> being moved into the master executor. There is no need for a spearate process
> anymore since there isn't going to be a separate storage engine that may need
> to make calls to this process. The lob file processing can all be done in
> the master process itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1871) UPDATE STATS fails with error 2006 when default charset is UTF8
[ https://issues.apache.org/jira/browse/TRAFODION-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183353#comment-15183353 ] ASF GitHub Bot commented on TRAFODION-1871: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/362 > UPDATE STATS fails with error 2006 when default charset is UTF8 > --- > > Key: TRAFODION-1871 > URL: https://issues.apache.org/jira/browse/TRAFODION-1871 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmu >Affects Versions: 2.0-incubating, 1.3-incubating > Environment: All >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall > > When the default character set is set to UTF8 (for example, by setting the > value 'UTF8" for default 'DEFAULT_CHARSET' in the system defaults table, or > by issuing CQD DEFAULT_CHARSET 'UTF8'), UPDATE STATS may fail with an > assertion error 2006 when done on a table that already has statistics. > A workaround is known: First clear the statistics (by doing UPDATE STATISTICS > FOR TABLE table-name CLEAR;) before generating new statistics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1866) Build should not require qmake
[ https://issues.apache.org/jira/browse/TRAFODION-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183359#comment-15183359 ] ASF GitHub Bot commented on TRAFODION-1866: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/355 > Build should not require qmake > -- > > Key: TRAFODION-1866 > URL: https://issues.apache.org/jira/browse/TRAFODION-1866 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau >Assignee: Steve Varnau > > SQL Query Debugger is an optional component. Building it may be skipped by > not having QT_TOOLKIT set to valid directory. In this case, make should not > even use qmake, which is part of the toolkit (also available in qt-devel > RPM). Trafodion should build without having qmake installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1879) Integrate library management into Trafodion metadata
Roberta Marton created TRAFODION-1879: - Summary: Integrate library management into Trafodion metadata Key: TRAFODION-1879 URL: https://issues.apache.org/jira/browse/TRAFODION-1879 Project: Apache Trafodion Issue Type: Improvement Components: sql-cmu Reporter: Roberta Marton Assignee: Roberta Marton The initial release of library management has been delivered to Trafodion. This is a follow-on JIRA that integrates library management operations into the existing Trafodion infrastructure. Currently, with the initial release of library management, the consumer needs to run a special script to set up everything. This JIRA will incorporate the steps into existing SQL commands and remove the need for the script. To enable library management, a new schema is created. In the schema, a library and set of procedures are created. In addition, if authorization is enable, a new role is created and granted execute privileges (with grant option) on all procedures. Integrating library management into Trafodion will be done by adding new options (create, drop, and upgrade) to the INITIALIZE TRAFODION command - INITIALIZE TRAFODION, CREATE LIBRARY MANAGEMENT: This command creates the SEABASE_LIBMGR_SCHEMA, creates the SEABASE_LIBMGR_LIBRARY, and creates all the procedures as described in the init_libmgmt.sh script. • SEABASE_LIBMGR_SCHEMA is "_LIBMGR_" • SEABASE_LIBMGR_LIBRARY is "DB__LIBMGRNAME" (Note - SEABASE_LIBMGR_SCHEMA is set to "_LIBMGR_" instead of DB__LIBMGR. This name was chosen to meet current architecture standards for Trafodion. Any schema beginning and ending with an underscore is considered system system. System schemas are treated special – for example, a person cannot drop the schema or create their own private objects in the schema. We want this schema to be considered a system schema.) If authorization is enabled, then role DB__LIBMGRROLE is granted execute privilege with the WITH GRANT OPTION on all procedures. INITIALIZE TRAFODION, DROP LIBRARY MANAGEMENT: This command drops the SEABASE_LIBMGR_SCHEMA. INITIALIZE TRAFODION, UPGRADE LIBRARY MANAGEMENT: This command verifies that the SEABASE_LIBMGR_LIBRARY exists and adds any new procedures. It will not drop or alter existing procedures. Once we externalize these procedures, we cannot drop or alter them without some kind of upgrade operation. For example, if a user is actively using one of these procedures, dropping or changing them could cause the customer's application to fail. If you do need to change something like their signatures, it might be easier to add a new procedure. If you want to drop them, then we need some mechanism to "obsolete" them for a release or two before actually removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1866) Build should not require qmake
[ https://issues.apache.org/jira/browse/TRAFODION-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Varnau closed TRAFODION-1866. --- Resolution: Fixed Fix Version/s: 2.0-incubating > Build should not require qmake > -- > > Key: TRAFODION-1866 > URL: https://issues.apache.org/jira/browse/TRAFODION-1866 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau >Assignee: Steve Varnau > Fix For: 2.0-incubating > > > SQL Query Debugger is an optional component. Building it may be skipped by > not having QT_TOOLKIT set to valid directory. In this case, make should not > even use qmake, which is part of the toolkit (also available in qt-devel > RPM). Trafodion should build without having qmake installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[
https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183390#comment-15183390
]
ASF GitHub Bot commented on TRAFODION-1863:
---
Github user selvaganesang commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/364#discussion_r55246253
--- Diff: core/sql/optimizer/ValueDesc.cpp ---
@@ -529,14 +529,13 @@ NABoolean ValueId::isAddedColumnWithNonNullDefault()
const{
default:
break;
}
- if (nac && nac->isAddedColumn() && nac->getDefaultValue())
+ if (nac && nac->getDefaultValue() &&
strcmp(nac->getDefaultValue(),"NULL") != 0)
--- End diff --
Will it be better to check for DefaultColumnClass == COM_NULL_DEFAULT
instead.
> With hbase_filter_preds set to '2', wrong results are returned for a specific
> use case.
> ---
>
> Key: TRAFODION-1863
> URL: https://issues.apache.org/jira/browse/TRAFODION-1863
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Eric Owhadi
>
> create table t056t57 (a1 numeric(2,2) signed default 0 not null);
> showddl t056t57;
> insert into t056t57 default values;
> select * from t056t57;
> >>select * from t056t57 ;
> A1
> ---
> .00
> --- 1 row(s) selected.
> >>cqd hbase_filter_preds '2' ;
> --- SQL operation complete.
> >>select * from t056t57 ;
> ..
> --- 0 row(s) selected.
> >>
> This was causing core/TEST056 to fail with PR #340.. Possibly similar issue
> is with core/TEST029 too, Currently this test case runs with
> hbase_filter_preds set to 'ON'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[
https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183415#comment-15183415
]
ASF GitHub Bot commented on TRAFODION-1863:
---
Github user eowhadi commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/364#discussion_r55248094
--- Diff: core/sql/optimizer/ValueDesc.cpp ---
@@ -529,14 +529,13 @@ NABoolean ValueId::isAddedColumnWithNonNullDefault()
const{
default:
break;
}
- if (nac && nac->isAddedColumn() && nac->getDefaultValue())
+ if (nac && nac->getDefaultValue() &&
strcmp(nac->getDefaultValue(),"NULL") != 0)
--- End diff --
why is it better? I know what I do work. I don't know about the
alternative. But I know how much a re run of regression cost :-)
> With hbase_filter_preds set to '2', wrong results are returned for a specific
> use case.
> ---
>
> Key: TRAFODION-1863
> URL: https://issues.apache.org/jira/browse/TRAFODION-1863
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Eric Owhadi
>
> create table t056t57 (a1 numeric(2,2) signed default 0 not null);
> showddl t056t57;
> insert into t056t57 default values;
> select * from t056t57;
> >>select * from t056t57 ;
> A1
> ---
> .00
> --- 1 row(s) selected.
> >>cqd hbase_filter_preds '2' ;
> --- SQL operation complete.
> >>select * from t056t57 ;
> ..
> --- 0 row(s) selected.
> >>
> This was causing core/TEST056 to fail with PR #340.. Possibly similar issue
> is with core/TEST029 too, Currently this test case runs with
> hbase_filter_preds set to 'ON'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1828) DCS - Remove unneeded dependent jars
[ https://issues.apache.org/jira/browse/TRAFODION-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183515#comment-15183515 ] ASF GitHub Bot commented on TRAFODION-1828: --- GitHub user hegdean opened a pull request: https://github.com/apache/incubator-trafodion/pull/370 [TRAFODION-1828] DCS - Remove unneeded dependent jars You can merge this pull request into a Git repository by running: $ git pull https://github.com/hegdean/incubator-trafodion wrkbrnch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/370.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 #370 commit 7fe6dd13600a931986769fb30c886ca6efb7c7ee Author: Anuradha Hegde Date: 2016-03-05T17:24:44Z Removed the unused and declared dependencies. > DCS - Remove unneeded dependent jars > > > Key: TRAFODION-1828 > URL: https://issues.apache.org/jira/browse/TRAFODION-1828 > Project: Apache Trafodion > Issue Type: Sub-task >Reporter: Steve Varnau >Assignee: Anuradha Hegde >Priority: Minor > > To reduce binary distribution license work we need to minimize the number of > third-party jar files bundled with DCS. Eliminate unnecessary ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[
https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183717#comment-15183717
]
ASF GitHub Bot commented on TRAFODION-1863:
---
Github user zellerh commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/364#discussion_r55272393
--- Diff: core/sql/generator/GenPreCode.cpp ---
@@ -11386,7 +11386,7 @@ NABoolean
HbaseAccess::isHbaseFilterPredV2(Generator * generator, ItemExpr * ie,
}
//check if not an added column with default non null
if ((foundBinary || foundUnary)&& (NOT hbaseLookupPred)){
-if (colVID.isAddedColumnWithNonNullDefault()){
+if (colVID.isColumnWithNonNullDefault()){
--- End diff --
Would a check for added columns with non-null default be sufficient for
aligned format?
> With hbase_filter_preds set to '2', wrong results are returned for a specific
> use case.
> ---
>
> Key: TRAFODION-1863
> URL: https://issues.apache.org/jira/browse/TRAFODION-1863
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Eric Owhadi
>
> create table t056t57 (a1 numeric(2,2) signed default 0 not null);
> showddl t056t57;
> insert into t056t57 default values;
> select * from t056t57;
> >>select * from t056t57 ;
> A1
> ---
> .00
> --- 1 row(s) selected.
> >>cqd hbase_filter_preds '2' ;
> --- SQL operation complete.
> >>select * from t056t57 ;
> ..
> --- 0 row(s) selected.
> >>
> This was causing core/TEST056 to fail with PR #340.. Possibly similar issue
> is with core/TEST029 too, Currently this test case runs with
> hbase_filter_preds set to 'ON'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[
https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183719#comment-15183719
]
ASF GitHub Bot commented on TRAFODION-1863:
---
Github user zellerh commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/364#discussion_r55272540
--- Diff: core/sql/optimizer/ValueDesc.cpp ---
@@ -529,14 +529,13 @@ NABoolean ValueId::isAddedColumnWithNonNullDefault()
const{
default:
break;
}
- if (nac && nac->isAddedColumn() && nac->getDefaultValue())
+ if (nac && nac->getDefaultValue() &&
strcmp(nac->getDefaultValue(),"NULL") != 0)
--- End diff --
Agree with Selva that checking the enum is safer and more maintainable.
Maybe you can make this change in a future check-in, so you don't have to rerun
the regressions just for that?
> With hbase_filter_preds set to '2', wrong results are returned for a specific
> use case.
> ---
>
> Key: TRAFODION-1863
> URL: https://issues.apache.org/jira/browse/TRAFODION-1863
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Eric Owhadi
>
> create table t056t57 (a1 numeric(2,2) signed default 0 not null);
> showddl t056t57;
> insert into t056t57 default values;
> select * from t056t57;
> >>select * from t056t57 ;
> A1
> ---
> .00
> --- 1 row(s) selected.
> >>cqd hbase_filter_preds '2' ;
> --- SQL operation complete.
> >>select * from t056t57 ;
> ..
> --- 0 row(s) selected.
> >>
> This was causing core/TEST056 to fail with PR #340.. Possibly similar issue
> is with core/TEST029 too, Currently this test case runs with
> hbase_filter_preds set to 'ON'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[
https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183725#comment-15183725
]
ASF GitHub Bot commented on TRAFODION-1863:
---
Github user eowhadi commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/364#discussion_r55273061
--- Diff: core/sql/generator/GenPreCode.cpp ---
@@ -11386,7 +11386,7 @@ NABoolean
HbaseAccess::isHbaseFilterPredV2(Generator * generator, ItemExpr * ie,
}
//check if not an added column with default non null
if ((foundBinary || foundUnary)&& (NOT hbaseLookupPred)){
-if (colVID.isAddedColumnWithNonNullDefault()){
+if (colVID.isColumnWithNonNullDefault()){
--- End diff --
this code is totally bypassed for align format
> With hbase_filter_preds set to '2', wrong results are returned for a specific
> use case.
> ---
>
> Key: TRAFODION-1863
> URL: https://issues.apache.org/jira/browse/TRAFODION-1863
> Project: Apache Trafodion
> Issue Type: Bug
>Reporter: Selvaganesan Govindarajan
>Assignee: Eric Owhadi
>
> create table t056t57 (a1 numeric(2,2) signed default 0 not null);
> showddl t056t57;
> insert into t056t57 default values;
> select * from t056t57;
> >>select * from t056t57 ;
> A1
> ---
> .00
> --- 1 row(s) selected.
> >>cqd hbase_filter_preds '2' ;
> --- SQL operation complete.
> >>select * from t056t57 ;
> ..
> --- 0 row(s) selected.
> >>
> This was causing core/TEST056 to fail with PR #340.. Possibly similar issue
> is with core/TEST029 too, Currently this test case runs with
> hbase_filter_preds set to 'ON'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1880) Download libhdfs dependency instead of building from source
Steve Varnau created TRAFODION-1880: --- Summary: Download libhdfs dependency instead of building from source Key: TRAFODION-1880 URL: https://issues.apache.org/jira/browse/TRAFODION-1880 Project: Apache Trafodion Issue Type: Bug Reporter: Steve Varnau Trafodion build process picks up libhdfs / libhadoop dependencies either from local_hadoop test set-up or by building them from source code. Building them from source more than doubles trafodion build time. Previously the the hadoop-common binary distro did not contain native 64-bit shared libraries. Now that it does, we can take advantage of that and not build from source code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-1880) Download libhdfs dependency instead of building from source
[ https://issues.apache.org/jira/browse/TRAFODION-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Varnau reassigned TRAFODION-1880: --- Assignee: Steve Varnau > Download libhdfs dependency instead of building from source > --- > > Key: TRAFODION-1880 > URL: https://issues.apache.org/jira/browse/TRAFODION-1880 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau >Assignee: Steve Varnau > > Trafodion build process picks up libhdfs / libhadoop dependencies either from > local_hadoop test set-up or by building them from source code. > Building them from source more than doubles trafodion build time. > Previously the the hadoop-common binary distro did not contain native 64-bit > shared libraries. Now that it does, we can take advantage of that and not > build from source code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1880) Download libhdfs dependency instead of building from source
[ https://issues.apache.org/jira/browse/TRAFODION-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183762#comment-15183762 ] Steve Varnau commented on TRAFODION-1880: - We need to consolidate hdfs dependency so that maven jars and shared libs pick up same version. We should separate build-time and test-time dependencies. > Download libhdfs dependency instead of building from source > --- > > Key: TRAFODION-1880 > URL: https://issues.apache.org/jira/browse/TRAFODION-1880 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Steve Varnau > > Trafodion build process picks up libhdfs / libhadoop dependencies either from > local_hadoop test set-up or by building them from source code. > Building them from source more than doubles trafodion build time. > Previously the the hadoop-common binary distro did not contain native 64-bit > shared libraries. Now that it does, we can take advantage of that and not > build from source code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[ https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184054#comment-15184054 ] ASF GitHub Bot commented on TRAFODION-1863: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/364 > With hbase_filter_preds set to '2', wrong results are returned for a specific > use case. > --- > > Key: TRAFODION-1863 > URL: https://issues.apache.org/jira/browse/TRAFODION-1863 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Selvaganesan Govindarajan >Assignee: Eric Owhadi > > create table t056t57 (a1 numeric(2,2) signed default 0 not null); > showddl t056t57; > insert into t056t57 default values; > select * from t056t57; > >>select * from t056t57 ; > A1 > --- > .00 > --- 1 row(s) selected. > >>cqd hbase_filter_preds '2' ; > --- SQL operation complete. > >>select * from t056t57 ; > .. > --- 0 row(s) selected. > >> > This was causing core/TEST056 to fail with PR #340.. Possibly similar issue > is with core/TEST029 too, Currently this test case runs with > hbase_filter_preds set to 'ON' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1863) With hbase_filter_preds set to '2', wrong results are returned for a specific use case.
[ https://issues.apache.org/jira/browse/TRAFODION-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Owhadi updated TRAFODION-1863: --- fix with PR364 > With hbase_filter_preds set to '2', wrong results are returned for a specific > use case. > --- > > Key: TRAFODION-1863 > URL: https://issues.apache.org/jira/browse/TRAFODION-1863 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Selvaganesan Govindarajan >Assignee: Eric Owhadi > > create table t056t57 (a1 numeric(2,2) signed default 0 not null); > showddl t056t57; > insert into t056t57 default values; > select * from t056t57; > >>select * from t056t57 ; > A1 > --- > .00 > --- 1 row(s) selected. > >>cqd hbase_filter_preds '2' ; > --- SQL operation complete. > >>select * from t056t57 ; > .. > --- 0 row(s) selected. > >> > This was causing core/TEST056 to fail with PR #340.. Possibly similar issue > is with core/TEST029 too, Currently this test case runs with > hbase_filter_preds set to 'ON' -- 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 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
[
https://issues.apache.org/jira/browse/TRAFODION-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Commented] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column
[
https://issues.apache.org/jira/browse/TRAFODION-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184331#comment-15184331
]
ASF GitHub Bot commented on TRAFODION-1858:
---
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafodion/pull/347
> 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] [Resolved] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column
[
https://issues.apache.org/jira/browse/TRAFODION-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liu ming resolved TRAFODION-1858.
-
Resolution: Fixed
Fix Version/s: 2.0-incubating
> 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] [Closed] (TRAFODION-1858) RI predicate generating string should not contain _SALT_ column
[
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] [Updated] (TRAFODION-1875) 'sqnodeipcrm' script failed to parse node name during sqstart
[ 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] [Updated] (TRAFODION-1878) Create a docker environment
[ 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] [Resolved] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified
[ 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] [Work stopped] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified
[ 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] [Work started] (TRAFODION-1834) ESP colocation (CQD TRAF_ALLOW_ESP_COLOCATION) not working when node names in sqconfig are fully qualified
[ 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 started] (TRAFODION-1878) Create a docker environment
[ https://issues.apache.org/jira/browse/TRAFODION-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1878 started by 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)
