[jira] [Resolved] (HAWQ-1131) Fix error message difference between Orca and Planner
[ https://issues.apache.org/jira/browse/HAWQ-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-1131. - Resolution: Fixed Fix Version/s: 2.0.1.0-incubating > Fix error message difference between Orca and Planner > - > > Key: HAWQ-1131 > URL: https://issues.apache.org/jira/browse/HAWQ-1131 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > Fix For: 2.0.1.0-incubating > > > In ORCA, due to the way exception handled previously we do warning first > and then later print error referring that message. Only a single message > should be printed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-934) Populate canSetTag of PlannedStmt from Query object
[ https://issues.apache.org/jira/browse/HAWQ-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-934. Resolution: Fixed > Populate canSetTag of PlannedStmt from Query object > --- > > Key: HAWQ-934 > URL: https://issues.apache.org/jira/browse/HAWQ-934 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Venkatesh > Fix For: 2.0.1.0-incubating > > > HAWQ generated an error if a single query resulted in multiple query plans > because of rule transformation and the plans were produced by PQO. This is > because of an incorrect directive in the plan to lock the same resource more > than once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-938) Remove ivy.xml in gpopt and read orca version from header file
[ https://issues.apache.org/jira/browse/HAWQ-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-938. Resolution: Fixed > Remove ivy.xml in gpopt and read orca version from header file > -- > > Key: HAWQ-938 > URL: https://issues.apache.org/jira/browse/HAWQ-938 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > Fix For: 2.0.1.0-incubating > > > Currently, if we want to upgrade orca or gpos, we need change the orca SHA as > well as the version number in ivy.xml. The function gp_opt_version() returns > version number that is read from ivy.xml, which is not a right way. It should > only be dependent on the source file of orca and gpos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-983) Minirepro generate wrong dependency order of objects and miss CTE relations
[ https://issues.apache.org/jira/browse/HAWQ-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-983. Resolution: Fixed > Minirepro generate wrong dependency order of objects and miss CTE relations > --- > > Key: HAWQ-983 > URL: https://issues.apache.org/jira/browse/HAWQ-983 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > Fix For: 2.0.1.0-incubating > > > The minirepro generate scripts in the wrong dependency order if dtabase > relations are in different schemas. In addition, it misses relations in CTE > and function objects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-929) Fix plan generated by query window function and no partition by clause
[ https://issues.apache.org/jira/browse/HAWQ-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-929. Resolution: Resolved > Fix plan generated by query window function and no partition by clause > -- > > Key: HAWQ-929 > URL: https://issues.apache.org/jira/browse/HAWQ-929 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Venkatesh > Fix For: 2.0.1.0-incubating > > > Bump ORCA version to 1.637 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-860) Optimizer generates wrong plan when correlated subquery contains set-returning functions
[ https://issues.apache.org/jira/browse/HAWQ-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-860. Resolution: Fixed > Optimizer generates wrong plan when correlated subquery contains > set-returning functions > > > Key: HAWQ-860 > URL: https://issues.apache.org/jira/browse/HAWQ-860 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Venkatesh >Assignee: Haisheng Yuan > Fix For: 2.0.1.0-incubating > > > Bump ORCA to 1.634 [#119042413] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-1122) Bump ORCA version to 1.674
[ https://issues.apache.org/jira/browse/HAWQ-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-1122. - Resolution: Resolved Fix Version/s: 2.0.1.0-incubating > Bump ORCA version to 1.674 > -- > > Key: HAWQ-1122 > URL: https://issues.apache.org/jira/browse/HAWQ-1122 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: xin zhang >Assignee: Lei Chang > Fix For: 2.0.1.0-incubating > > > This improvement will port related changes under `src/backend/gpopt` from > GPDB OSS to use GPORCA version v1.674. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1137) Remove banned api mechanism in Orca
Haisheng Yuan created HAWQ-1137: --- Summary: Remove banned api mechanism in Orca Key: HAWQ-1137 URL: https://issues.apache.org/jira/browse/HAWQ-1137 Project: Apache HAWQ Issue Type: Improvement Components: Optimizer Reporter: Haisheng Yuan Assignee: Lei Chang gporca has a set of banned API calls which needs to be allowed with the ALLOW_xxx macro in order for gpopt to compile. But it should be the library caller (HAWQ)'s responsibility to take care of the function call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-1137) Remove banned api mechanism in Orca
[ https://issues.apache.org/jira/browse/HAWQ-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned HAWQ-1137: --- Assignee: Haisheng Yuan (was: Lei Chang) > Remove banned api mechanism in Orca > --- > > Key: HAWQ-1137 > URL: https://issues.apache.org/jira/browse/HAWQ-1137 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > > gporca has a set of banned API calls which needs to be allowed with the > ALLOW_xxx macro in order for gpopt to compile. But it should be the library > caller (HAWQ)'s responsibility to take care of the function call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1136) Disable .psqlrc in minirepro
Haisheng Yuan created HAWQ-1136:
---
Summary: Disable .psqlrc in minirepro
Key: HAWQ-1136
URL: https://issues.apache.org/jira/browse/HAWQ-1136
Project: Apache HAWQ
Issue Type: Bug
Components: Command Line Tools
Reporter: Haisheng Yuan
Assignee: Lei Chang
.psqlrc can create unexpected output and changes in formatting that don't play
nice with parse_oids().
```
psql database --pset footer -Atq -h localhost -p 5432 -U gpadmin -f
/tmp/20161012232709/toolkit.sql
{"relids": "573615536", "funcids": ""}
Time: 2.973 ms
```
Generates an Exception:
```
Traceback (most recent call last):
File "/usr/local/greenplum-db/./bin/minirepro", line 386, in
main()
File "/usr/local/greenplum-db/./bin/minirepro", line 320, in main
mr_query = parse_oids(cursor, json_str)
File "/usr/local/greenplum-db/./bin/minirepro", line 151, in parse_oids
result.relids = json.loads(json_oids)['relids']
File "/usr/local/greenplum-db/ext/python/lib/python2.6/json/__init__.py",
line 307, in loads
return _default_decoder.decode(s)
File "/usr/local/greenplum-db/ext/python/lib/python2.6/json/decoder.py", line
322, in decode
raise ValueError(errmsg("Extra data", s, end, len(s)))
ValueError: Extra data: line 2 column 1 - line 3 column 1 (char 39 - 54)
```
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HAWQ-1136) Disable .psqlrc in minirepro
[
https://issues.apache.org/jira/browse/HAWQ-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haisheng Yuan reassigned HAWQ-1136:
---
Assignee: Haisheng Yuan (was: Lei Chang)
> Disable .psqlrc in minirepro
>
>
> Key: HAWQ-1136
> URL: https://issues.apache.org/jira/browse/HAWQ-1136
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Command Line Tools
>Reporter: Haisheng Yuan
>Assignee: Haisheng Yuan
>
> .psqlrc can create unexpected output and changes in formatting that don't
> play nice with parse_oids().
> ```
> psql database --pset footer -Atq -h localhost -p 5432 -U gpadmin -f
> /tmp/20161012232709/toolkit.sql
> {"relids": "573615536", "funcids": ""}
> Time: 2.973 ms
> ```
> Generates an Exception:
> ```
> Traceback (most recent call last):
> File "/usr/local/greenplum-db/./bin/minirepro", line 386, in
> main()
> File "/usr/local/greenplum-db/./bin/minirepro", line 320, in main
> mr_query = parse_oids(cursor, json_str)
> File "/usr/local/greenplum-db/./bin/minirepro", line 151, in parse_oids
> result.relids = json.loads(json_oids)['relids']
> File "/usr/local/greenplum-db/ext/python/lib/python2.6/json/__init__.py",
> line 307, in loads
> return _default_decoder.decode(s)
> File "/usr/local/greenplum-db/ext/python/lib/python2.6/json/decoder.py",
> line 322, in decode
> raise ValueError(errmsg("Extra data", s, end, len(s)))
> ValueError: Extra data: line 2 column 1 - line 3 column 1 (char 39 - 54)
> ```
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HAWQ-1131) Fix error message difference between Orca and Planner
[ https://issues.apache.org/jira/browse/HAWQ-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned HAWQ-1131: --- Assignee: Haisheng Yuan (was: Lei Chang) > Fix error message difference between Orca and Planner > - > > Key: HAWQ-1131 > URL: https://issues.apache.org/jira/browse/HAWQ-1131 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > > In ORCA, due to the way exception handled previously we do warning first > and then later print error referring that message. Only a single message > should be printed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-1131) Fix error message difference between Orca and Planner
[ https://issues.apache.org/jira/browse/HAWQ-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-1131: Summary: Fix error message difference between Orca and Planner (was: Fix error message between Orca and Planner) > Fix error message difference between Orca and Planner > - > > Key: HAWQ-1131 > URL: https://issues.apache.org/jira/browse/HAWQ-1131 > Project: Apache HAWQ > Issue Type: Bug > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Lei Chang > > In ORCA, due to the way exception handled previously we do warning first > and then later print error referring that message. Only a single message > should be printed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1131) Fix error message between Orca and Planner
Haisheng Yuan created HAWQ-1131: --- Summary: Fix error message between Orca and Planner Key: HAWQ-1131 URL: https://issues.apache.org/jira/browse/HAWQ-1131 Project: Apache HAWQ Issue Type: Bug Components: Optimizer Reporter: Haisheng Yuan Assignee: Lei Chang In ORCA, due to the way exception handled previously we do warning first and then later print error referring that message. Only a single message should be printed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-1093) Bump Orca version and enable Orca related exception propagation
[ https://issues.apache.org/jira/browse/HAWQ-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned HAWQ-1093: --- Assignee: Haisheng Yuan (was: Lei Chang) > Bump Orca version and enable Orca related exception propagation > --- > > Key: HAWQ-1093 > URL: https://issues.apache.org/jira/browse/HAWQ-1093 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-983) Minirepro generate wrong dependency order of objects and miss CTE relations
Haisheng Yuan created HAWQ-983: -- Summary: Minirepro generate wrong dependency order of objects and miss CTE relations Key: HAWQ-983 URL: https://issues.apache.org/jira/browse/HAWQ-983 Project: Apache HAWQ Issue Type: Bug Components: Command Line Tools Reporter: Haisheng Yuan Assignee: Lei Chang The minirepro generate scripts in the wrong dependency order if dtabase relations are in different schemas. In addition, it misses relations in CTE and function objects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-938) Remove ivy.xml in gpopt and read orca version from header file
[ https://issues.apache.org/jira/browse/HAWQ-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned HAWQ-938: -- Assignee: Haisheng Yuan (was: Venkatesh) > Remove ivy.xml in gpopt and read orca version from header file > -- > > Key: HAWQ-938 > URL: https://issues.apache.org/jira/browse/HAWQ-938 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Haisheng Yuan > Fix For: 2.0.1.0-incubating > > > Currently, if we want to upgrade orca or gpos, we need change the orca SHA as > well as the version number in ivy.xml. The function gp_opt_version() returns > version number that is read from ivy.xml, which is not a right way. It should > only be dependent on the source file of orca and gpos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-938) Remove ivy.xml in gpopt and read orca version from header file
[ https://issues.apache.org/jira/browse/HAWQ-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-938: --- Description: Currently, if we want to upgrade orca or gpos, we need change the orca SHA as well as the version number in ivy.xml. The function gp_opt_version() returns version number that is read from ivy.xml, which is not a right way. It should only be dependent on the source file of orca and gpos. (was: Currently, if we want to upgrade orca or gpos, we need change the orca SHA as well as the version number in ivy.xml. The function qp_opt_version() returns version number that is read from ivy.xml, which is not a right way. It should only be dependent on the source file of orca and gpos.) > Remove ivy.xml in gpopt and read orca version from header file > -- > > Key: HAWQ-938 > URL: https://issues.apache.org/jira/browse/HAWQ-938 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Venkatesh > > Currently, if we want to upgrade orca or gpos, we need change the orca SHA as > well as the version number in ivy.xml. The function gp_opt_version() returns > version number that is read from ivy.xml, which is not a right way. It should > only be dependent on the source file of orca and gpos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-938) Remove ivy.xml in gpopt and read orca version from header file
Haisheng Yuan created HAWQ-938: -- Summary: Remove ivy.xml in gpopt and read orca version from header file Key: HAWQ-938 URL: https://issues.apache.org/jira/browse/HAWQ-938 Project: Apache HAWQ Issue Type: Improvement Components: Optimizer Reporter: Haisheng Yuan Assignee: Venkatesh Currently, if we want to upgrade orca or gpos, we need change the orca SHA as well as the version number in ivy.xml. The function qp_opt_version() returns version number that is read from ivy.xml, which is not a right way. It should only be dependent on the source file of orca and gpos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-936) Add GUC for array expansion in ORCA optimizer
Haisheng Yuan created HAWQ-936:
--
Summary: Add GUC for array expansion in ORCA optimizer
Key: HAWQ-936
URL: https://issues.apache.org/jira/browse/HAWQ-936
Project: Apache HAWQ
Issue Type: New Feature
Components: Optimizer
Reporter: Haisheng Yuan
Assignee: Venkatesh
Consider the query with the following pattern select * from foo where foo.a IN
{1,2,3,...}. Currently, when the number of constants in the IN subquery is
large, the query optimization time is unacceptable. This is stopping customers
from turning Orca on by default since many of the queries are generated queries
with such a pattern.
The root cause is due to the expansion of the IN subquery into an expression in
disjunctive normal form. The objective of this story is to disable this
expansion when the number of constants in the IN list is large.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HAWQ-934) Populate canSetTag of PlannedStmt from Query object
Haisheng Yuan created HAWQ-934: -- Summary: Populate canSetTag of PlannedStmt from Query object Key: HAWQ-934 URL: https://issues.apache.org/jira/browse/HAWQ-934 Project: Apache HAWQ Issue Type: Bug Components: Optimizer Reporter: Haisheng Yuan Assignee: Venkatesh HAWQ generated an error if a single query resulted in multiple query plans because of rule transformation and the plans were produced by PQO. This is because of an incorrect directive in the plan to lock the same resource more than once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (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 resolved HAWQ-763. Resolution: Fixed > 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] [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] [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] [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)
[jira] [Updated] (HAWQ-670) Error when changing the table distribution policy from random to hash distribution
[
https://issues.apache.org/jira/browse/HAWQ-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haisheng Yuan updated HAWQ-670:
---
Description:
If the current segments number is 8 and I run these queries,
{code:sql}
create table t2 (c1 int) with (bucketnum=5);
create table t2_2 (c2 int) inherits(t2);
alter table t2 set distributed by (c1);
{code}
The alter table clause will show the following error message:
{color:red}
ERROR: bucketnum requires a numeric value
{color}
which is not expected behavior.
The query should be able to be executed without error messages.
was:
If the current segments number is 8 and I run these queries,
{code:sql}
create table t2 (c1 int) with (bucketnum=5);
create table t2_2 (c2 int) inherits(t2);
alter table t2 set distributed by (c1);
{code}
The alter table clause will show the following error message:
{color:red}
ERROR: bucketnum requires a numeric value
{color}
which is not expected behavior.
The query should be able to be executed without error messages.
> Error when changing the table distribution policy from random to hash
> distribution
> --
>
> Key: HAWQ-670
> URL: https://issues.apache.org/jira/browse/HAWQ-670
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: Haisheng Yuan
>Assignee: Lei Chang
>
> If the current segments number is 8 and I run these queries,
> {code:sql}
> create table t2 (c1 int) with (bucketnum=5);
> create table t2_2 (c2 int) inherits(t2);
> alter table t2 set distributed by (c1);
> {code}
> The alter table clause will show the following error message:
> {color:red}
> ERROR: bucketnum requires a numeric value
> {color}
> which is not expected behavior.
> The query should be able to be executed without error messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HAWQ-404) Add sort during INSERT of append only row oriented partition tables
[ https://issues.apache.org/jira/browse/HAWQ-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-404. Resolution: Fixed > Add sort during INSERT of append only row oriented partition tables > --- > > Key: HAWQ-404 > URL: https://issues.apache.org/jira/browse/HAWQ-404 > Project: Apache HAWQ > Issue Type: Improvement >Reporter: Haisheng Yuan >Assignee: Lei Chang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-646) Bump up optimizer version number
Haisheng Yuan created HAWQ-646: -- Summary: Bump up optimizer version number Key: HAWQ-646 URL: https://issues.apache.org/jira/browse/HAWQ-646 Project: Apache HAWQ Issue Type: Improvement Components: Optimizer Reporter: Haisheng Yuan Assignee: Amr El-Helw -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-455) Disable creating partition tables with non uniform bucket schema
[ https://issues.apache.org/jira/browse/HAWQ-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-455. Resolution: Fixed Resolved in commit: https://github.com/apache/incubator-hawq/commit/d72d0fa041953c66e1663ce8952f0191b12bf8a1 > Disable creating partition tables with non uniform bucket schema > - > > Key: HAWQ-455 > URL: https://issues.apache.org/jira/browse/HAWQ-455 > Project: Apache HAWQ > Issue Type: Improvement > Components: DDL >Reporter: Haisheng Yuan >Assignee: Lei Chang > > HAWQ user should not be able to create partition tables with non uniform > bucket schema so that don't make orca trip up when it queries across a single > partition. Or else the user should see an error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-455) Disable creating partition tables with non uniform bucket schema
Haisheng Yuan created HAWQ-455: -- Summary: Disable creating partition tables with non uniform bucket schema Key: HAWQ-455 URL: https://issues.apache.org/jira/browse/HAWQ-455 Project: Apache HAWQ Issue Type: Improvement Components: DDL Reporter: Haisheng Yuan Assignee: Lei Chang HAWQ user should not be able to create partition tables with non uniform bucket schema so that don't make orca trip up when it queries across a single partition. Or else the user should see an error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-404) Add sort during INSERT of append only row oriented partition tables
Haisheng Yuan created HAWQ-404: -- Summary: Add sort during INSERT of append only row oriented partition tables Key: HAWQ-404 URL: https://issues.apache.org/jira/browse/HAWQ-404 Project: Apache HAWQ Issue Type: Improvement Reporter: Haisheng Yuan Assignee: Lei Chang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-161) Port GPDB planner fixes to HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-161. Resolution: Resolved > Port GPDB planner fixes to HAWQ > --- > > Key: HAWQ-161 > URL: https://issues.apache.org/jira/browse/HAWQ-161 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Amr El-Helw >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-324) Add minirepro to let user dump minimal set of DDL and statistics for a given query
[ https://issues.apache.org/jira/browse/HAWQ-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15109116#comment-15109116 ] Haisheng Yuan commented on HAWQ-324: It was resolved. I will close it. > Add minirepro to let user dump minimal set of DDL and statistics for a given > query > -- > > Key: HAWQ-324 > URL: https://issues.apache.org/jira/browse/HAWQ-324 > Project: Apache HAWQ > Issue Type: Improvement > Components: Command Line Tools >Reporter: Haisheng Yuan >Assignee: Lei Chang > > As a Database User, I should be able to dump the DDL and Statistics > Information for a given query so I don't have to dump a large GPDB file. > GIVEN I am a Database User > WHEN I run minirepro database-name -q sql-file-name -f output-file-name > THEN I should get the DDL and statistics info for the tables and views > accessed in that query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-123) Add 'Partition by' description in psql
[ https://issues.apache.org/jira/browse/HAWQ-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved HAWQ-123. Resolution: Resolved > Add 'Partition by' description in psql > -- > > Key: HAWQ-123 > URL: https://issues.apache.org/jira/browse/HAWQ-123 > Project: Apache HAWQ > Issue Type: Improvement > Components: Command Line Tools >Reporter: Haisheng Yuan >Assignee: Lei Chang >Priority: Minor > > As a Data Engineer, I should be able to see partition key in psql so that I > can better understand the schema of the partition table. > GIVEN I am a Data Engineer > WHEN I run \d on a partition table > THEN I should see the partition key of the current level in the output > Notes: > the sub-children will not be displayed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-324) Add minirepro to let user dump minimal set of DDL and statistics for a given query
Haisheng Yuan created HAWQ-324: -- Summary: Add minirepro to let user dump minimal set of DDL and statistics for a given query Key: HAWQ-324 URL: https://issues.apache.org/jira/browse/HAWQ-324 Project: Apache HAWQ Issue Type: Improvement Components: Command Line Tools Reporter: Haisheng Yuan Assignee: Lei Chang As a Database User, I should be able to dump the DDL and Statistics Information for a given query so I don't have to dump a large GPDB file. GIVEN I am a Database User WHEN I run minirepro database-name -q sql-file-name -f output-file-name THEN I should get the DDL and statistics info for the tables and views accessed in that query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-161) Port GPDB planner fixes to HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-161: --- Priority: Minor (was: Major) > Port GPDB planner fixes to HAWQ > --- > > Key: HAWQ-161 > URL: https://issues.apache.org/jira/browse/HAWQ-161 > Project: Apache HAWQ > Issue Type: Improvement > Components: Optimizer >Reporter: Haisheng Yuan >Assignee: Amr El-Helw >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-161) Port GPDB planner fixes to HAWQ
Haisheng Yuan created HAWQ-161: -- Summary: Port GPDB planner fixes to HAWQ Key: HAWQ-161 URL: https://issues.apache.org/jira/browse/HAWQ-161 Project: Apache HAWQ Issue Type: Improvement Components: Optimizer Reporter: Haisheng Yuan Assignee: Amr El-Helw -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-123) Add 'Partition by' description in psql
[ https://issues.apache.org/jira/browse/HAWQ-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-123: --- Summary: Add 'Partition by' description in psql (was: Data Engineer can see partition key in psql) > Add 'Partition by' description in psql > -- > > Key: HAWQ-123 > URL: https://issues.apache.org/jira/browse/HAWQ-123 > Project: Apache HAWQ > Issue Type: Improvement > Components: Command Line Tools >Reporter: Haisheng Yuan >Assignee: Lei Chang >Priority: Minor > > As a Data Engineer, I should be able to see partition key in psql so that I > can better understand the schema of the partition table. > GIVEN I am a Data Engineer > WHEN I run \d on a partition table > THEN I should see the partition key of the current level in the output > Notes: > the sub-children will not be displayed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-123) Data Engineer can see partition key in psql
[ https://issues.apache.org/jira/browse/HAWQ-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated HAWQ-123: --- Priority: Minor (was: Major) > Data Engineer can see partition key in psql > --- > > Key: HAWQ-123 > URL: https://issues.apache.org/jira/browse/HAWQ-123 > Project: Apache HAWQ > Issue Type: Improvement > Components: Command Line Tools >Reporter: Haisheng Yuan >Assignee: Lei Chang >Priority: Minor > > As a Data Engineer, I should be able to see partition key in psql so that I > can better understand the schema of the partition table. > GIVEN I am a Data Engineer > WHEN I run \d on a partition table > THEN I should see the partition key of the current level in the output > Notes: > the sub-children will not be displayed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
