[jira] [Commented] (HAWQ-743) RPM conflict between apache-tomcat and pxf-service
[
https://issues.apache.org/jira/browse/HAWQ-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305746#comment-15305746
]
ASF GitHub Bot commented on HAWQ-743:
-
Github user hsyuan commented on the pull request:
https://github.com/apache/incubator-hawq/pull/666#issuecomment-222340959
+1
> RPM conflict between apache-tomcat and pxf-service
> --
>
> Key: HAWQ-743
> URL: https://issues.apache.org/jira/browse/HAWQ-743
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Build
>Reporter: Zhanwei Wang
>Assignee: Zhanwei Wang
>
> {code}
> ==
> Package 架构
> 版本源
> 大小
> ==
> 正在安装:
> pxf-service noarch
> 3.0.0-22126 HDB
> 212 k
> 事务概要
> ==
> 安装 1 软件包
> 总计：212 k
> 安装大小：371 k
> Is this ok [y/d/N]: y
> Downloading packages:
> Running transaction check
> Running transaction test
> Transaction check error:
> file /opt/pivotal from install of pxf-service-0:3.0.0-22126.noarch
> conflicts with file from package apache-tomcat-0:7.0.62-.noarch
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HAWQ-713) lc_numeric guc doesn't behave as expected after some time
[
https://issues.apache.org/jira/browse/HAWQ-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305745#comment-15305745
]
ASF GitHub Bot commented on HAWQ-713:
-
Github user hsyuan commented on the pull request:
https://github.com/apache/incubator-hawq/pull/652#issuecomment-222340934
👍
+1
> lc_numeric guc doesn't behave as expected after some time
> -
>
> Key: HAWQ-713
> URL: https://issues.apache.org/jira/browse/HAWQ-713
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Core
>Reporter: Karthikeyan Jambu Rajaraman
>Assignee: Lei Chang
> Attachments: lc_numeric_check.out, lc_numeric_check.sql
>
>
> Create a simple table with a 1,1 value in it that we will change based on
> lc_numeric. Default we are expecting will be 11 but 1.1 under de_DE
> {code}
> gpadmin=# \d tbl_lc_numeric_test
> Table "public.tbl_lc_numeric_test"
> Column | Type | Modifiers
> +---+---
> a | text |
> s | character varying(50) |
> Distributed by: (a)
> gpadmin=# select * from tbl_lc_numeric_test;
> a | s
> -+---
> 3 | blablabla
> 1,1 | bla
> 2 | blabla
> (3 rows)
> {code}
> When lc_numeric is changed 'de_DE.utf8' as shown below, '1,1' is printed as
> '1.1' as expected.
> {code}
> gpadmin=# set lc_numeric='de_DE.utf8';
> SET
> gpadmin=# show lc_numeric
> gpadmin-# ;
> lc_numeric
>
> de_DE.utf8
> (1 row)
> gpadmin=# \echo `date`
> Thu Apr 21 10:05:00 PDT 2016
> gpadmin=# select to_number(a,'99D9')::numeric(10,5), s from
> tbl_lc_numeric_test;
> to_number | s
> ---+---
>1.1 | bla
>3.0 | blablabla
>2.0 | blabla
> (3 rows)
> {code}
> But if we run above select again after some time (after idle gang timeout),
> then we saw the value as 11 instead of 1.1.
> {code}
> gpadmin=# \echo `date`
> Thu Apr 21 10:05:30 PDT 2016
> gpadmin=# select to_number(a,'99D9')::numeric(10,5), s from
> tbl_lc_numeric_test;
> to_number | s
> ---+---
>3.0 | blablabla
>2.0 | blabla
> 11.0 | bla
> (3 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HAWQ-763) Remove traceflag that allows ORCA to run in multiple threads
[ https://issues.apache.org/jira/browse/HAWQ-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-763: --- Component/s: Optimizer > Remove traceflag that allows ORCA to run in multiple threads > > > Key: HAWQ-763 > URL: https://issues.apache.org/jira/browse/HAWQ-763 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Lei Chang > > We are integrating VEM with GPOS memory allocator. VMEM is not thread safe. > So, ORCA/GPOS also need to be single threaded. Currently, HAWQ users are > using only the single threaded Orca. > So need to remove the traceflag that allows ORCA to run in multiple threads > so that HAWQ users do not accidentally run ORCA in multiple threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-764) Remove CTranslatorPlStmtToDXL Deadcode
[ https://issues.apache.org/jira/browse/HAWQ-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-764: --- Component/s: Optimizer > Remove CTranslatorPlStmtToDXL Deadcode > -- > > Key: HAWQ-764 > URL: https://issues.apache.org/jira/browse/HAWQ-764 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Lei Chang > > When we did not have optimization modules in Orca and just DXL, we used > CTranslatorPlStmtToDXL to test correctness of translation of DXL to PlStmt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-765) Remove CTranslatorDXLToQuery Deadcode
[ https://issues.apache.org/jira/browse/HAWQ-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305743#comment-15305743 ] ASF GitHub Bot commented on HAWQ-765: - Github user hsyuan commented on the pull request: https://github.com/apache/incubator-hawq/pull/661#issuecomment-222340720 Apache HAWQ JIRA issue was created for this PR: https://issues.apache.org/jira/browse/HAWQ-765 > Remove CTranslatorDXLToQuery Deadcode > - > > Key: HAWQ-765 > URL: https://issues.apache.org/jira/browse/HAWQ-765 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Amr El-Helw > > When we did not have optimization modules in Orca and just DXL, we used > CTranslatorDXLToQuery to test correctness of translation of Query to DXL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-765) Remove CTranslatorDXLToQuery Deadcode
Haisheng Yuan created HAWQ-765: -- Summary: Remove CTranslatorDXLToQuery Deadcode Key: HAWQ-765 URL: https://issues.apache.org/jira/browse/HAWQ-765 Project: Apache HAWQ Issue Type: Improvement Components: Optimizer Reporter: Haisheng Yuan Assignee: Amr El-Helw When we did not have optimization modules in Orca and just DXL, we used CTranslatorDXLToQuery to test correctness of translation of Query to DXL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-764) Remove CTranslatorPlStmtToDXL Deadcode
[ https://issues.apache.org/jira/browse/HAWQ-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305742#comment-15305742 ] ASF GitHub Bot commented on HAWQ-764: - Github user hsyuan commented on the pull request: https://github.com/apache/incubator-hawq/pull/646#issuecomment-222340666 HAWQ JIRA issue was created for this PR: https://issues.apache.org/jira/browse/HAWQ-764 @vraghavan78 Please update this PR. > Remove CTranslatorPlStmtToDXL Deadcode > -- > > Key: HAWQ-764 > URL: https://issues.apache.org/jira/browse/HAWQ-764 > Project: Apache HAWQ > Issue Type: Improvement >Reporter: Haisheng Yuan >Assignee: Lei Chang > > When we did not have optimization modules in Orca and just DXL, we used > CTranslatorPlStmtToDXL to test correctness of translation of DXL to PlStmt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-764) Remove CTranslatorPlStmtToDXL Deadcode
Haisheng Yuan created HAWQ-764: -- Summary: Remove CTranslatorPlStmtToDXL Deadcode Key: HAWQ-764 URL: https://issues.apache.org/jira/browse/HAWQ-764 Project: Apache HAWQ Issue Type: Improvement Reporter: Haisheng Yuan Assignee: Lei Chang When we did not have optimization modules in Orca and just DXL, we used CTranslatorPlStmtToDXL to test correctness of translation of DXL to PlStmt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-763) Remove traceflag that allows ORCA to run in multiple threads
[ https://issues.apache.org/jira/browse/HAWQ-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305738#comment-15305738 ] ASF GitHub Bot commented on HAWQ-763: - Github user hsyuan commented on the pull request: https://github.com/apache/incubator-hawq/pull/644#issuecomment-222340582 Create HAWQ JIRA issue for this PR: https://issues.apache.org/jira/browse/HAWQ-763 @vraghavan78 please change this PR title and commit message starting with `HAWQ-763. Remove traceflag that allows ORCA to run in multiple threads`, which follows the apache HAWQ PR requirement. > Remove traceflag that allows ORCA to run in multiple threads > > > Key: HAWQ-763 > URL: https://issues.apache.org/jira/browse/HAWQ-763 > Project: Apache HAWQ > Issue Type: Improvement >Reporter: Haisheng Yuan >Assignee: Lei Chang > > We are integrating VEM with GPOS memory allocator. VMEM is not thread safe. > So, ORCA/GPOS also need to be single threaded. Currently, HAWQ users are > using only the single threaded Orca. > So need to remove the traceflag that allows ORCA to run in multiple threads > so that HAWQ users do not accidentally run ORCA in multiple threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-763) Remove traceflag that allows ORCA to run in multiple threads
Haisheng Yuan created HAWQ-763: -- Summary: Remove traceflag that allows ORCA to run in multiple threads Key: HAWQ-763 URL: https://issues.apache.org/jira/browse/HAWQ-763 Project: Apache HAWQ Issue Type: Improvement Reporter: Haisheng Yuan Assignee: Lei Chang We are integrating VEM with GPOS memory allocator. VMEM is not thread safe. So, ORCA/GPOS also need to be single threaded. Currently, HAWQ users are using only the single threaded Orca. So need to remove the traceflag that allows ORCA to run in multiple threads so that HAWQ users do not accidentally run ORCA in multiple threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
