[jira] [Commented] (HAWQ-1437) Hadoop enabled Kerberos，HAWQ occurs errors
[
https://issues.apache.org/jira/browse/HAWQ-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977206#comment-15977206
]
Oleksandr Diachenko commented on HAWQ-1437:
---
[~lynnyuan] try this:
pxfautomation=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month
text, num_orders int, total_sales float8) LOCATION
('pxf://mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
FORMAT 'TEXT' (delimiter=E',');
It should work if you have "mycluster" as a nameservice configured in HDFS.
> Hadoop enabled Kerberos，HAWQ occurs errors
> --
>
> Key: HAWQ-1437
> URL: https://issues.apache.org/jira/browse/HAWQ-1437
> Project: Apache HAWQ
> Issue Type: Bug
> Components: PXF
>Reporter: lynn
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> When kerberos enabled with Hadoop , HAWQ create external table from hdfs need
> principal information， what should I do can create it success?
> postgres=#
> postgres=#
> postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month
> text, num_orders int, total_sales float8)
> postgres-# LOCATION
> ('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
> postgres-# FORMAT 'TEXT' (delimiter=E',');
> ERROR: Invalid URI
> pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple
> : missing authority section
> postgres=#
> postgres=#
> postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month
> text, num_orders int, total_sales float8)
> postgres-# LOCATION
> ('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA')
> postgres-# FORMAT 'TEXT' (delimiter=E',');
> ERROR: Invalid URI
> pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA
> : missing authority section
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (HAWQ-1438) Analyze report error: relcache reference xxx is not owned by resource owner TopTransaction
[ https://issues.apache.org/jira/browse/HAWQ-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976843#comment-15976843 ] Ming LI edited comment on HAWQ-1438 at 4/20/17 2:59 PM: The PR abstract: (1) Add TopResourceOwner to trace resource used beyond the transaction boundary. (2) When to auto alloc a new TopResourceOwner for each process? Generate a singleton TopResourceOwner when setting CurrentResourceOwner to NULL. (3) If crashed at some code beyond the transaction boundary, we should manually create a new resource owner, because we do manually create a new one for each process. (4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for each process? Register it at on_proc_exit(). was (Author: mli): The PR introduction: (1) Add TopResourceOwner to trace resource used beyond the transaction boundary. (2) When to auto alloc a new TopResourceOwner for each process? Generate a singleton TopResourceOwner when setting CurrentResourceOwner to NULL. (3) If crashed at some code beyond the transaction boundary, we should manually create a new resource owner, because we do manually create a new one for each process. (4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for each process? Register it at on_proc_exit(). > Analyze report error: relcache reference xxx is not owned by resource owner > TopTransaction > -- > > Key: HAWQ-1438 > URL: https://issues.apache.org/jira/browse/HAWQ-1438 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Reporter: Ming LI >Assignee: Ed Espino > Fix For: backlog > > > 2017-04-12 14:23:13.866064 > BST,"mis_ig","ig",p124811,th-224249568,"10.33.188.8","5172",2017-04-12 > 14:20:42 > BST,76687174,con61,cmd16,seg-1,,,x76687174,sx1,"ERROR","XX000","relcache > reference e_event_1_0_102_1_prt_2 is not owned by resource owner > TopTransaction (resowner.c:766)",,"ANALYZE > mis_data_ig_account_details.e_event_1_0_102",0,,"resowner.c",766,"Stack trace: > 1 0x8ce438 postgres errstart (elog.c:492) > 2 0x8d01bb postgres elog_finish (elog.c:1443) > 3 0x4ca5f4 postgres relation_close (heapam.c:1267) > 4 0x5e7498 postgres analyzeStmt (analyze.c:728) > 5 0x5e8a97 postgres analyzeStatement (analyze.c:274) > 6 0x65c34c postgres vacuum (vacuum.c:319) > 7 0x7f6172 postgres ProcessUtility (utility.c:1472) > 8 0x7f1c3e postgres (pquery.c:1974) > 9 0x7f341e postgres (pquery.c:2078) > 10 0x7f5185 postgres PortalRun (pquery.c:1599) > 11 0x7ee1f8 postgres PostgresMain (postgres.c:2782) > 12 0x7a04f0 postgres (postmaster.c:5486) > 13 0x7a32b9 postgres PostmasterMain (postmaster.c:1459) > 14 0x4a52b9 postgres main (main.c:226) > 15 0x7fcaee7ded5d libc.so.6 __libc_start_main (??:0) > 16 0x4a5339 postgres (??:0) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1438) Analyze report error: relcache reference xxx is not owned by resource owner TopTransaction
[ https://issues.apache.org/jira/browse/HAWQ-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976843#comment-15976843 ] Ming LI commented on HAWQ-1438: --- The PR introduction: (1) Add TopResourceOwner to trace resource used beyond the transaction boundary. (2) When to auto alloc a new TopResourceOwner for each process? Generate a singleton TopResourceOwner when setting CurrentResourceOwner to NULL. (3) If crashed at some code beyond the transaction boundary, we should manually create a new resource owner, because we do manually create a new one for each process. (4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for each process? Register it at on_proc_exit(). > Analyze report error: relcache reference xxx is not owned by resource owner > TopTransaction > -- > > Key: HAWQ-1438 > URL: https://issues.apache.org/jira/browse/HAWQ-1438 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Reporter: Ming LI >Assignee: Ed Espino > Fix For: backlog > > > 2017-04-12 14:23:13.866064 > BST,"mis_ig","ig",p124811,th-224249568,"10.33.188.8","5172",2017-04-12 > 14:20:42 > BST,76687174,con61,cmd16,seg-1,,,x76687174,sx1,"ERROR","XX000","relcache > reference e_event_1_0_102_1_prt_2 is not owned by resource owner > TopTransaction (resowner.c:766)",,"ANALYZE > mis_data_ig_account_details.e_event_1_0_102",0,,"resowner.c",766,"Stack trace: > 1 0x8ce438 postgres errstart (elog.c:492) > 2 0x8d01bb postgres elog_finish (elog.c:1443) > 3 0x4ca5f4 postgres relation_close (heapam.c:1267) > 4 0x5e7498 postgres analyzeStmt (analyze.c:728) > 5 0x5e8a97 postgres analyzeStatement (analyze.c:274) > 6 0x65c34c postgres vacuum (vacuum.c:319) > 7 0x7f6172 postgres ProcessUtility (utility.c:1472) > 8 0x7f1c3e postgres (pquery.c:1974) > 9 0x7f341e postgres (pquery.c:2078) > 10 0x7f5185 postgres PortalRun (pquery.c:1599) > 11 0x7ee1f8 postgres PostgresMain (postgres.c:2782) > 12 0x7a04f0 postgres (postmaster.c:5486) > 13 0x7a32b9 postgres PostmasterMain (postmaster.c:1459) > 14 0x4a52b9 postgres main (main.c:226) > 15 0x7fcaee7ded5d libc.so.6 __libc_start_main (??:0) > 16 0x4a5339 postgres (??:0) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1222: HAWQ-1438. Support resource owner beyond ...
GitHub user liming01 opened a pull request: https://github.com/apache/incubator-hawq/pull/1222 HAWQ-1438. Support resource owner beyond transaction boundary (1) Add TopResourceOwner to trace resource used beyond the transaction boundary. (2) When to auto alloc a new TopResourceOwner for each process? Generate a singleton TopResourceOwner when setting CurrentResourceOwner to NULL. (3) If crashed at some code beyond the transaction boundary, we should manually create a new resource owner, because we do manually create a new one for each process. (4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for each process? Register it at on_proc_exit(). You can merge this pull request into a Git repository by running: $ git pull https://github.com/liming01/incubator-hawq mli/resownerOutTx Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1222.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 #1222 commit 049f5ff6c0f98b4b7224d97b5b926a58a06cce54 Author: Ming LI Date: 2017-04-20T09:04:51Z HAWQ-1438. Support resource owner beyond transaction boundary (1) Add TopResourceOwner to trace resource used beyond the transaction boundary. (2) When to auto alloc a new TopResourceOwner for each process? Generate a singleton TopResourceOwner when setting CurrentResourceOwner to NULL. (3) If crashed at some code beyond the transaction boundary, we should manually create a new resource owner, because we do manually create a new one for each process. (4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for each process? Register it at on_proc_exit(). --- 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-1438) Analyze report error: relcache reference xxx is not owned by resource owner TopTransaction
[ https://issues.apache.org/jira/browse/HAWQ-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976335#comment-15976335 ] Ming LI commented on HAWQ-1438: --- This defect is caused by the fix at HAWQ-1417. Now the resource owner can not be used beyond the transaction boundary. > Analyze report error: relcache reference xxx is not owned by resource owner > TopTransaction > -- > > Key: HAWQ-1438 > URL: https://issues.apache.org/jira/browse/HAWQ-1438 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Reporter: Ming LI >Assignee: Ed Espino > Fix For: backlog > > > 2017-04-12 14:23:13.866064 > BST,"mis_ig","ig",p124811,th-224249568,"10.33.188.8","5172",2017-04-12 > 14:20:42 > BST,76687174,con61,cmd16,seg-1,,,x76687174,sx1,"ERROR","XX000","relcache > reference e_event_1_0_102_1_prt_2 is not owned by resource owner > TopTransaction (resowner.c:766)",,"ANALYZE > mis_data_ig_account_details.e_event_1_0_102",0,,"resowner.c",766,"Stack trace: > 1 0x8ce438 postgres errstart (elog.c:492) > 2 0x8d01bb postgres elog_finish (elog.c:1443) > 3 0x4ca5f4 postgres relation_close (heapam.c:1267) > 4 0x5e7498 postgres analyzeStmt (analyze.c:728) > 5 0x5e8a97 postgres analyzeStatement (analyze.c:274) > 6 0x65c34c postgres vacuum (vacuum.c:319) > 7 0x7f6172 postgres ProcessUtility (utility.c:1472) > 8 0x7f1c3e postgres (pquery.c:1974) > 9 0x7f341e postgres (pquery.c:2078) > 10 0x7f5185 postgres PortalRun (pquery.c:1599) > 11 0x7ee1f8 postgres PostgresMain (postgres.c:2782) > 12 0x7a04f0 postgres (postmaster.c:5486) > 13 0x7a32b9 postgres PostmasterMain (postmaster.c:1459) > 14 0x4a52b9 postgres main (main.c:226) > 15 0x7fcaee7ded5d libc.so.6 __libc_start_main (??:0) > 16 0x4a5339 postgres (??:0) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HAWQ-1438) Analyze report error: relcache reference xxx is not owned by resource owner TopTransaction
Ming LI created HAWQ-1438: - Summary: Analyze report error: relcache reference xxx is not owned by resource owner TopTransaction Key: HAWQ-1438 URL: https://issues.apache.org/jira/browse/HAWQ-1438 Project: Apache HAWQ Issue Type: Bug Components: Core Reporter: Ming LI Assignee: Ed Espino Fix For: backlog 2017-04-12 14:23:13.866064 BST,"mis_ig","ig",p124811,th-224249568,"10.33.188.8","5172",2017-04-12 14:20:42 BST,76687174,con61,cmd16,seg-1,,,x76687174,sx1,"ERROR","XX000","relcache reference e_event_1_0_102_1_prt_2 is not owned by resource owner TopTransaction (resowner.c:766)",,"ANALYZE mis_data_ig_account_details.e_event_1_0_102",0,,"resowner.c",766,"Stack trace: 1 0x8ce438 postgres errstart (elog.c:492) 2 0x8d01bb postgres elog_finish (elog.c:1443) 3 0x4ca5f4 postgres relation_close (heapam.c:1267) 4 0x5e7498 postgres analyzeStmt (analyze.c:728) 5 0x5e8a97 postgres analyzeStatement (analyze.c:274) 6 0x65c34c postgres vacuum (vacuum.c:319) 7 0x7f6172 postgres ProcessUtility (utility.c:1472) 8 0x7f1c3e postgres (pquery.c:1974) 9 0x7f341e postgres (pquery.c:2078) 10 0x7f5185 postgres PortalRun (pquery.c:1599) 11 0x7ee1f8 postgres PostgresMain (postgres.c:2782) 12 0x7a04f0 postgres (postmaster.c:5486) 13 0x7a32b9 postgres PostmasterMain (postmaster.c:1459) 14 0x4a52b9 postgres main (main.c:226) 15 0x7fcaee7ded5d libc.so.6 __libc_start_main (??:0) 16 0x4a5339 postgres (??:0) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
