[jira] [Commented] (HAWQ-1220) Support ranger plugin server HA in hawq side.
[ https://issues.apache.org/jira/browse/HAWQ-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15747574#comment-15747574 ] Lili Ma commented on HAWQ-1220: --- I think RPS(Ranger Plugin Service) is independent from master/standby master, which means, there may exist HAWQ master fail but RPS on hawq master still alive, and another side that HAWQ standby master fail but RPS on hawq standby master still alive, right? In current implementation, we just include start RPS in "hawq start master" and "hawq start standby". But whatever HAWQ master or HAWQ standby master, it will check the RPS service on the same host with it, if finding failure, will try to connect another RPS, right? Thanks > Support ranger plugin server HA in hawq side. > - > > Key: HAWQ-1220 > URL: https://issues.apache.org/jira/browse/HAWQ-1220 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Security >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: backlog > > > RPS will run both at master and at standby master, If connection to master > RPS failed, we should try to connect to standby master instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-1220) Support ranger plugin server HA in hawq side.
[ https://issues.apache.org/jira/browse/HAWQ-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert Zhang reassigned HAWQ-1220: -- Assignee: Hubert Zhang (was: Ed Espino) > Support ranger plugin server HA in hawq side. > - > > Key: HAWQ-1220 > URL: https://issues.apache.org/jira/browse/HAWQ-1220 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Security >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: backlog > > > RPS will run both at master and at standby master, If connection to master > RPS failed, we should try to connect to standby master instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1220) Support ranger plugin server HA in hawq side.
Hubert Zhang created HAWQ-1220: -- Summary: Support ranger plugin server HA in hawq side. Key: HAWQ-1220 URL: https://issues.apache.org/jira/browse/HAWQ-1220 Project: Apache HAWQ Issue Type: Sub-task Components: Security Reporter: Hubert Zhang Assignee: Ed Espino RPS will run both at master and at standby master, If connection to master RPS failed, we should try to connect to standby master instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #1047: HAWQ-1003. Implement batched ACL check th...
Github user zhangh43 commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1047#discussion_r92317681 --- Diff: src/backend/utils/misc/guc.c --- @@ -8154,6 +8174,15 @@ static struct config_string ConfigureNamesString[] = }, { +{"hawq_rps_address_host", PGC_POSTMASTER, PRESET_OPTIONS, + gettext_noop("rps server address hostname"), + NULL +}, +_addr_host, +"localhost", NULL, NULL + }, + + { --- End diff -- fixed --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1047: HAWQ-1003. Implement batched ACL check th...
Github user zhangh43 commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1047#discussion_r92317685 --- Diff: src/backend/utils/misc/guc.c --- @@ -6250,6 +6261,15 @@ static struct config_int ConfigureNamesInt[] = }, { +{"hawq_rps_address_port", PGC_POSTMASTER, PRESET_OPTIONS, + gettext_noop("rps server address port number"), + NULL +}, +_addr_port, +1, 1, 65535, NULL, NULL + }, + + { --- End diff -- fixed --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #1047: HAWQ-1003. Implement batched ACL check th...
Github user zhangh43 commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1047#discussion_r92317398 --- Diff: src/backend/parser/parse_relation.c --- @@ -2713,15 +2712,90 @@ warnAutoRange(ParseState *pstate, RangeVar *relation, int location) void ExecCheckRTPerms(List *rangeTable) { + if (enable_ranger) + { +if(rangeTable!=NULL) + ExecCheckRTPermsWithRanger(rangeTable); +return; + } ListCell *l; - foreach(l, rangeTable) { ExecCheckRTEPerms((RangeTblEntry *) lfirst(l)); } } /* + * ExecCheckRTPerms + * Batch implementation: Check access permissions for all relations listed in a range table with enable_ranger is true. + */ +void +ExecCheckRTPermsWithRanger(List *rangeTable) +{ + List *ranger_check_args = NIL; + ListCell *l; + foreach(l, rangeTable) + { + +AclMode requiredPerms; +Oid relOid; +Oid userid; +RangeTblEntry *rte = (RangeTblEntry *) lfirst(l); + +if (rte->rtekind != RTE_RELATION) + return; +requiredPerms = rte->requiredPerms; +if (requiredPerms == 0) + return; + +relOid = rte->relid; +userid = rte->checkAsUser ? rte->checkAsUser : GetUserId(); + +RangerPrivilegeArgs *ranger_check_arg = (RangerPrivilegeArgs *) palloc(sizeof(RangerPrivilegeArgs)); +ranger_check_arg->objkind = ACL_KIND_CLASS; +ranger_check_arg->object_oid = relOid; +ranger_check_arg->roleid = userid; +ranger_check_arg->mask = requiredPerms; +ranger_check_arg->how = ACLMASK_ALL; +ranger_check_args = lappend(ranger_check_args, ranger_check_arg); + + } // foreach + + // ranger ACL check with package Oids + List *aclresults = NIL; + aclresults = pg_rangercheck_batch(ranger_check_args); + if (aclresults == NIL) + { +elog(ERROR, "ERROR\n"); --- End diff -- yes, this error message should be replaced by the exact error message in future. for example, which table doesn't pass the acl check. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq issue #1040: HAWQ-1195. Fixed error "Two or more external tab...
Github user wangzw commented on the issue: https://github.com/apache/incubator-hawq/pull/1040 Hi guys, please see the comments in the JIRA. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (HAWQ-1195) Synchrony:Union not working on external tables ERROR:"Two or more external tables use the same error table ""xxxxxxx"" in a statement (execMain.c:274)"
[ https://issues.apache.org/jira/browse/HAWQ-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15747072#comment-15747072 ] Zhanwei Wang commented on HAWQ-1195: It's me who added such constrain that one error table cannot be used in the same query more than once. And I still think this constrain is valid right now. External table is usually used in two cases. 1) loading data from external data source and 2) export cold data into external storage to save cost. For the first case, error table is useful, but such external table is not suitable for query and even worse for complex query, because repeatedly running query on such table will cause error table expansion. User should import the data into a normal table and then run query on normal table. {code:sql} insert into normal_table select * from external_table; {code} For the second case, exported data is clean, and attaching an error table to an external table is useless. And if I remember clearly, if no dirty data exists in the external table, error table can be attached even if the external table is used more than once in the query without reporting error. So I think we should not break such constrain and keep report error in the case reported in this JIRA. > Synchrony:Union not working on external tables ERROR:"Two or more external > tables use the same error table ""xxx"" in a statement (execMain.c:274)" > --- > > Key: HAWQ-1195 > URL: https://issues.apache.org/jira/browse/HAWQ-1195 > Project: Apache HAWQ > Issue Type: Bug > Components: External Tables >Reporter: Ming LI >Assignee: Ming LI > Fix For: backlog > > > Hello, > User create an external table and define the error table. Then he do the > union on the same external table with different where condition. Then return > the error:ERROR: Two or more external tables use the same error table > "err_ext_pdr_cdci_pivotal_request_43448" in a statement (execMain.c:274) > Below is the master log when I reproduce: (the whole log file attached in > attachement) > {code} > 2016-11-29 22:49:51.976864 > PST,"gpadmin","postgres",p769199,th-2123704032,"[local]",,2016-11-29 22:46:14 > PST,1260,con72,cmd10,seg-1,,,x1260,sx1,"ERROR","XX000","Two or more external > tables use the same error table ""err_ext_pdr_cdci_pivotal_request_43448"" in > a statement (execMain.c:274)",,"select current_account_nbr,yearmonthint, > bank_name, first_date_open, max_cr_limit, care_credit_flag, cc1_flag, > partition_value, 'US' as loc from pdr_cdci_pivotal_request_43448 where > care_credit_flag<1 > union > select current_account_nbr,yearmonthint, bank_name, first_date_open, > max_cr_limit, care_credit_flag, cc1_flag, partition_value, 'Non-US' as loc > from pdr_cdci_pivotal_request_43448 where > care_credit_flag=1;",0,,"execMain.c",274,"Stack trace: > 10x8c5858 postgres errstart (??:0) > 20x8c75db postgres elog_finish (??:0) > 30x65f669 postgres (??:0) > 40x77d06a postgres walk_plan_node_fields (??:0) > 50x77e3ee postgres plan_tree_walker (??:0) > 60x77c70a postgres expression_tree_walker (??:0) > 70x77e35d postgres plan_tree_walker (??:0) > 80x77d06a postgres walk_plan_node_fields (??:0) > 90x77dfe6 postgres plan_tree_walker (??:0) > 10 0x77d06a postgres walk_plan_node_fields (??:0) > 11 0x77e1e5 postgres plan_tree_walker (??:0) > 12 0x77d06a postgres walk_plan_node_fields (??:0) > 13 0x77dfe6 postgres plan_tree_walker (??:0) > 14 0x77d06a postgres walk_plan_node_fields (??:0) > 15 0x77e1e5 postgres plan_tree_walker (??:0) > 16 0x66079b postgres ExecutorStart (??:0) > 17 0x7ebf1d postgres PortalStart (??:0) > 18 0x7e4288 postgres (??:0) > 19 0x7e54c2 postgres PostgresMain (??:0) > 20 0x797d50 postgres (??:0) > 21 0x79ab19 postgres PostmasterMain (??:0) > 22 0x4a4069 postgres main (??:0) > 23 0x7fd97d486d5d libc.so.6 __libc_start_main (??:0) > 24 0x4a40e9 postgres (??:0) > " > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #1040: HAWQ-1195. Fixed error "Two or more exter...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/1040 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (HAWQ-1192) document heap size and thread config setting recommendations for PXF
[ https://issues.apache.org/jira/browse/HAWQ-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746836#comment-15746836 ] ASF GitHub Bot commented on HAWQ-1192: -- Github user lisakowen closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/73 > document heap size and thread config setting recommendations for PXF > > > Key: HAWQ-1192 > URL: https://issues.apache.org/jira/browse/HAWQ-1192 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 2.0.0.0-incubating, 2.0.1.0-incubating >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > Fix For: 2.0.1.0-incubating > > > queries may hang or fail with Out of Memory Exception (OOM) in cases where > there are many concurrent requests and/or large file size. document specific > tomcat and PXF configuration setting recommendations to alleviate the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-1180) ALTER ROLE set statement should be removed from documentation
[ https://issues.apache.org/jira/browse/HAWQ-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jane Beckman resolved HAWQ-1180. Resolution: Fixed Fix Version/s: 2.0.1.0-incubating > ALTER ROLE set statement should be removed from documentation > - > > Key: HAWQ-1180 > URL: https://issues.apache.org/jira/browse/HAWQ-1180 > Project: Apache HAWQ > Issue Type: Task > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.0.1.0-incubating > > > ALTER ROLE SET statement returns: > ERROR: Cannot support alter role set statement yet > Sections instructing the user to use this function should be removed, for > example: > "You can also set search_path for a particular role (user) using the ALTER > ROLE command. For example: > => ALTER ROLE sally SET search_path TO myschema, public, > pg_catalog; “ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-1217) Clean up Catalog Table Reference section
[ https://issues.apache.org/jira/browse/HAWQ-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746818#comment-15746818 ] ASF GitHub Bot commented on HAWQ-1217: -- Github user janebeckman closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/72 > Clean up Catalog Table Reference section > > > Key: HAWQ-1217 > URL: https://issues.apache.org/jira/browse/HAWQ-1217 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.0.1.0-incubating > > > The Catalog Table Reference section has some instances of problematic formats > (spacing issues, typos, etc.), plus inconsistent use of formats. These should > be corrected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-1219) docs - pg_class ref page missing relstorage modes
[ https://issues.apache.org/jira/browse/HAWQ-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746787#comment-15746787 ] ASF GitHub Bot commented on HAWQ-1219: -- GitHub user lisakowen opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/74 HAWQ-1219 - add ao and parquet relstorage types add parquet and append only restorage types to pg_class reference page (table) You can merge this pull request into a Git repository by running: $ git pull https://github.com/lisakowen/incubator-hawq-docs feature/misc-updates-lo5 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/74.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 #74 commit 6bd32a39035a58cca66b5dbac0e165f126d6ca47 Author: Lisa OwenDate: 2016-12-09T22:26:24Z add ao and parquet relstorage types > docs - pg_class ref page missing relstorage modes > - > > Key: HAWQ-1219 > URL: https://issues.apache.org/jira/browse/HAWQ-1219 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Lisa Owen >Assignee: Ed Espino > > the pg_class reference page is missing the relstorage append-only and parquet > modes. add these to the table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1219) docs - pg_class ref page missing relstorage modes
Lisa Owen created HAWQ-1219: --- Summary: docs - pg_class ref page missing relstorage modes Key: HAWQ-1219 URL: https://issues.apache.org/jira/browse/HAWQ-1219 Project: Apache HAWQ Issue Type: Bug Reporter: Lisa Owen Assignee: Ed Espino the pg_class reference page is missing the relstorage append-only and parquet modes. add these to the table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-1218) docs - create reference page for DROP LANGUAGE
[ https://issues.apache.org/jira/browse/HAWQ-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen updated HAWQ-1218: Priority: Minor (was: Major) > docs - create reference page for DROP LANGUAGE > -- > > Key: HAWQ-1218 > URL: https://issues.apache.org/jira/browse/HAWQ-1218 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > > the DROP LANGUAGE SQL reference page is missing from the documentation. > create and add it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1218) docs - create reference page for DROP LANGUAGE
Lisa Owen created HAWQ-1218: --- Summary: docs - create reference page for DROP LANGUAGE Key: HAWQ-1218 URL: https://issues.apache.org/jira/browse/HAWQ-1218 Project: Apache HAWQ Issue Type: Improvement Components: Documentation Reporter: Lisa Owen Assignee: David Yozie the DROP LANGUAGE SQL reference page is missing from the documentation. create and add it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-1192) document heap size and thread config setting recommendations for PXF
[ https://issues.apache.org/jira/browse/HAWQ-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746760#comment-15746760 ] ASF GitHub Bot commented on HAWQ-1192: -- GitHub user lisakowen opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/73 HAWQ-1192 follow-up - simplify config change steps simplify the config change steps to case where PXF initialized and started. You can merge this pull request into a Git repository by running: $ git pull https://github.com/lisakowen/incubator-hawq-docs feature/HAWQ-1192-more Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/73.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 #73 > document heap size and thread config setting recommendations for PXF > > > Key: HAWQ-1192 > URL: https://issues.apache.org/jira/browse/HAWQ-1192 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 2.0.0.0-incubating, 2.0.1.0-incubating >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > Fix For: 2.0.1.0-incubating > > > queries may hang or fail with Out of Memory Exception (OOM) in cases where > there are many concurrent requests and/or large file size. document specific > tomcat and PXF configuration setting recommendations to alleviate the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-1217) Clean up Catalog Table Reference section
[ https://issues.apache.org/jira/browse/HAWQ-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746453#comment-15746453 ] ASF GitHub Bot commented on HAWQ-1217: -- GitHub user janebeckman opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/72 HAWQ-1217 Format cleanup Consistent code formatting, removal of duplicate sentence, typo correction. Removed gpdb statement from gp_segment_configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/janebeckman/incubator-hawq-docs feature/catalog_cleanup Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/72.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 #72 commit bad6ca1638dc4ac7bc3aec0cef0417bfb0a97338 Author: Jane BeckmanDate: 2016-12-10T01:27:20Z Format cleanup > Clean up Catalog Table Reference section > > > Key: HAWQ-1217 > URL: https://issues.apache.org/jira/browse/HAWQ-1217 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.0.1.0-incubating > > > The Catalog Table Reference section has some instances of problematic formats > (spacing issues, typos, etc.), plus inconsistent use of formats. These should > be corrected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1217) Clean up Catalog Table Reference section
Jane Beckman created HAWQ-1217: -- Summary: Clean up Catalog Table Reference section Key: HAWQ-1217 URL: https://issues.apache.org/jira/browse/HAWQ-1217 Project: Apache HAWQ Issue Type: Bug Components: Documentation Reporter: Jane Beckman Assignee: David Yozie Fix For: 2.0.1.0-incubating The Catalog Table Reference section has some instances of problematic formats (spacing issues, typos, etc.), plus inconsistent use of formats. These should be corrected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-722) Add Doc around how to use HAWQ via JDBC/ODBC/libpq et al.
[ https://issues.apache.org/jira/browse/HAWQ-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yozie resolved HAWQ-722. -- Resolution: Fixed Fix Version/s: 2.0.0.0-incubating > Add Doc around how to use HAWQ via JDBC/ODBC/libpq et al. > - > > Key: HAWQ-722 > URL: https://issues.apache.org/jira/browse/HAWQ-722 > Project: Apache HAWQ > Issue Type: New Feature > Components: Documentation >Reporter: Lei Chang >Assignee: David Yozie > Fix For: backlog, 2.0.0.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-1216) PL/Python doc page - validate and enhance info
[ https://issues.apache.org/jira/browse/HAWQ-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen updated HAWQ-1216: Priority: Minor (was: Major) > PL/Python doc page - validate and enhance info > -- > > Key: HAWQ-1216 > URL: https://issues.apache.org/jira/browse/HAWQ-1216 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > > PL/Python docs section: > - review and validate current content > - update module installation instructions - need to be root to install > modules to system python dirs > - make sure examples run and are relevant > - develop new examples as appropriate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-1216) PL/Python doc page - validate and enhance info
Lisa Owen created HAWQ-1216: --- Summary: PL/Python doc page - validate and enhance info Key: HAWQ-1216 URL: https://issues.apache.org/jira/browse/HAWQ-1216 Project: Apache HAWQ Issue Type: Improvement Components: Documentation Reporter: Lisa Owen Assignee: David Yozie PL/Python docs section: - review and validate current content - update module installation instructions - need to be root to install modules to system python dirs - make sure examples run and are relevant - develop new examples as appropriate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-1192) document heap size and thread config setting recommendations for PXF
[ https://issues.apache.org/jira/browse/HAWQ-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15745890#comment-15745890 ] ASF GitHub Bot commented on HAWQ-1192: -- Github user lisakowen closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/69 > document heap size and thread config setting recommendations for PXF > > > Key: HAWQ-1192 > URL: https://issues.apache.org/jira/browse/HAWQ-1192 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 2.0.0.0-incubating, 2.0.1.0-incubating >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > Fix For: 2.0.1.0-incubating > > > queries may hang or fail with Out of Memory Exception (OOM) in cases where > there are many concurrent requests and/or large file size. document specific > tomcat and PXF configuration setting recommendations to alleviate the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-1192) document heap size and thread config setting recommendations for PXF
[ https://issues.apache.org/jira/browse/HAWQ-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen resolved HAWQ-1192. - Resolution: Fixed Fix Version/s: 2.0.1.0-incubating added "Addressing PXF Memory Issues" section to "Troubleshooting PXF"" page. > document heap size and thread config setting recommendations for PXF > > > Key: HAWQ-1192 > URL: https://issues.apache.org/jira/browse/HAWQ-1192 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 2.0.0.0-incubating, 2.0.1.0-incubating >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > Fix For: 2.0.1.0-incubating > > > queries may hang or fail with Out of Memory Exception (OOM) in cases where > there are many concurrent requests and/or large file size. document specific > tomcat and PXF configuration setting recommendations to alleviate the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (HAWQ-1192) document heap size and thread config setting recommendations for PXF
[ https://issues.apache.org/jira/browse/HAWQ-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen closed HAWQ-1192. --- > document heap size and thread config setting recommendations for PXF > > > Key: HAWQ-1192 > URL: https://issues.apache.org/jira/browse/HAWQ-1192 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Affects Versions: 2.0.0.0-incubating, 2.0.1.0-incubating >Reporter: Lisa Owen >Assignee: David Yozie >Priority: Minor > Fix For: 2.0.1.0-incubating > > > queries may hang or fail with Out of Memory Exception (OOM) in cases where > there are many concurrent requests and/or large file size. document specific > tomcat and PXF configuration setting recommendations to alleviate the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)