[GitHub] incubator-hawq pull request #1279: HAWQ-1310. Reformat resource_negotiator()...

[linwen]

Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1279#discussion_r132612133
  
--- Diff: src/backend/optimizer/plan/planner.c ---
@@ -438,256 +438,224 @@ PlannedStmt *refineCachedPlan(PlannedStmt * 
plannedstmt,
  *
  
*/
 
-PlannedStmt * 
-planner(Query *parse, int cursorOptions,
-   ParamListInfo boundParams, QueryResourceLife resourceLife)
-{
-   PlannedStmt *result = NULL;
-   instr_time  starttime, endtime;
-   ResourceNegotiatorResult *ppResult = (ResourceNegotiatorResult *) 
palloc(sizeof(ResourceNegotiatorResult));
-   SplitAllocResult initResult = {NULL, NIL, 0, NIL, NULL};
-   ppResult->saResult = initResult;
-   ppResult->stmt = NULL;
-   static int plannerLevel = 0;
-   bool resourceNegotiateDone = false;
-   QueryResource *savedQueryResource = GetActiveQueryResource();
-   SetActiveRelType(NIL);
-
-   bool isDispatchParallel = false;
-   /*
-* Before doing the true query optimization, we first run a 
resource_negotiator to give
-* us some sense of the complexity of the query, and allocate the 
appropriate
-* resource to run this query. After gaining the resource, we can 
perform the
-* actual optimization.
-*/
-   increase_planning_depth();
-
-   plannerLevel++;
-   if (!resourceNegotiateDone)
-   {
- PG_TRY();
- {
-  START_MEMORY_ACCOUNT(MemoryAccounting_CreateAccount(0, 
MEMORY_OWNER_TYPE_Resource_Negotiator));
-  {
-resource_negotiator(parse, cursorOptions, boundParams, 
resourceLife, );
-
-   decrease_planning_depth();
-
-   if(ppResult->stmt && ppResult->stmt->planTree)
-   {
-   isDispatchParallel = ppResult->stmt->planTree->dispatch 
== DISPATCH_PARALLEL;
-   }
-  }
-  END_MEMORY_ACCOUNT();
- }
- PG_CATCH();
- {
-   decrease_planning_depth();
-
-   if ((ppResult != NULL))
-   {
- pfree(ppResult);
- ppResult = NULL;
-   }
-   plannerLevel = 0;
-   PG_RE_THROW();
- }
- PG_END_TRY();
-   }
-   SetActiveRelType(NIL);
-   if (plannerLevel >= 1)
-   {
- resourceNegotiateDone = true;
- gp_segments_for_planner = ppResult->saResult.planner_segments;
- if (ppResult->saResult.resource)
- {
-   SetActiveQueryResource(ppResult->saResult.resource);
-   SetActiveRelType(ppResult->saResult.relsType);
- }
-   }
+PlannedStmt *
+planner(Query *parse, int cursorOptions, ParamListInfo boundParams, 
QueryResourceLife resourceLife) {
+PlannedStmt *result = NULL;
+instr_time starttime, endtime;
+ResourceNegotiatorResult *ppResult = (ResourceNegotiatorResult *) 
palloc(sizeof(ResourceNegotiatorResult));
+SplitAllocResult initResult = { NULL, NIL, 0, NIL, NULL };
+ppResult->saResult = initResult;
+ppResult->stmt = NULL;
+static int plannerLevel = 0;
+bool resourceNegotiateDone = false;
+QueryResource *savedQueryResource = GetActiveQueryResource();
+SetActiveRelType(NIL);
+
+bool isDispatchParallel = false;
+/*
+ * Before doing the true query optimization, we first run a 
resource_negotiator to give
+ * us some sense of the complexity of the query, and allocate the 
appropriate
+ * resource to run this query. After gaining the resource, we can 
perform the
+ * actual optimization.
+ */
+increase_planning_depth();
+
+plannerLevel++;
+if (!resourceNegotiateDone) {
+PG_TRY();
+{
+START_MEMORY_ACCOUNT(MemoryAccounting_CreateAccount(0, 
MEMORY_OWNER_TYPE_Resource_Negotiator));
+{
+resource_negotiator(parse, cursorOptions, 
boundParams, resourceLife, );
+
+decrease_planning_depth();
+
+if (ppResult->stmt && ppResult->stmt->planTree) {
+isDispatchParallel = 
ppResult->stmt->planTree->dispatch == DISPATCH_PARALLEL;
+}
+}
+END_MEMORY_ACCOUNT();
+}PG_CATCH();
+{
+decrease_planning_depth();
+
+if ((ppResult != NULL)) {
+pfree(ppResult);
+ppResult = NULL;
+}
+plannerLevel = 0;
+PG_RE_THROW();
+}PG_END_TRY();
+}
+SetActiveRelType(NIL);
 

[GitHub] incubator-hawq pull request #1279: HAWQ-1310. Reformat resource_negotiator()...

[linwen]

Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1279#discussion_r132612181
  
--- Diff: src/backend/optimizer/plan/planner.c ---
@@ -438,256 +438,224 @@ PlannedStmt *refineCachedPlan(PlannedStmt * 
plannedstmt,
  *
  
*/
 
-PlannedStmt * 
-planner(Query *parse, int cursorOptions,
-   ParamListInfo boundParams, QueryResourceLife resourceLife)
-{
-   PlannedStmt *result = NULL;
-   instr_time  starttime, endtime;
-   ResourceNegotiatorResult *ppResult = (ResourceNegotiatorResult *) 
palloc(sizeof(ResourceNegotiatorResult));
-   SplitAllocResult initResult = {NULL, NIL, 0, NIL, NULL};
-   ppResult->saResult = initResult;
-   ppResult->stmt = NULL;
-   static int plannerLevel = 0;
-   bool resourceNegotiateDone = false;
-   QueryResource *savedQueryResource = GetActiveQueryResource();
-   SetActiveRelType(NIL);
-
-   bool isDispatchParallel = false;
-   /*
-* Before doing the true query optimization, we first run a 
resource_negotiator to give
-* us some sense of the complexity of the query, and allocate the 
appropriate
-* resource to run this query. After gaining the resource, we can 
perform the
-* actual optimization.
-*/
-   increase_planning_depth();
-
-   plannerLevel++;
-   if (!resourceNegotiateDone)
-   {
- PG_TRY();
- {
-  START_MEMORY_ACCOUNT(MemoryAccounting_CreateAccount(0, 
MEMORY_OWNER_TYPE_Resource_Negotiator));
-  {
-resource_negotiator(parse, cursorOptions, boundParams, 
resourceLife, );
-
-   decrease_planning_depth();
-
-   if(ppResult->stmt && ppResult->stmt->planTree)
-   {
-   isDispatchParallel = ppResult->stmt->planTree->dispatch 
== DISPATCH_PARALLEL;
-   }
-  }
-  END_MEMORY_ACCOUNT();
- }
- PG_CATCH();
- {
-   decrease_planning_depth();
-
-   if ((ppResult != NULL))
-   {
- pfree(ppResult);
- ppResult = NULL;
-   }
-   plannerLevel = 0;
-   PG_RE_THROW();
- }
- PG_END_TRY();
-   }
-   SetActiveRelType(NIL);
-   if (plannerLevel >= 1)
-   {
- resourceNegotiateDone = true;
- gp_segments_for_planner = ppResult->saResult.planner_segments;
- if (ppResult->saResult.resource)
- {
-   SetActiveQueryResource(ppResult->saResult.resource);
-   SetActiveRelType(ppResult->saResult.relsType);
- }
-   }
+PlannedStmt *
+planner(Query *parse, int cursorOptions, ParamListInfo boundParams, 
QueryResourceLife resourceLife) {
+PlannedStmt *result = NULL;
+instr_time starttime, endtime;
+ResourceNegotiatorResult *ppResult = (ResourceNegotiatorResult *) 
palloc(sizeof(ResourceNegotiatorResult));
+SplitAllocResult initResult = { NULL, NIL, 0, NIL, NULL };
+ppResult->saResult = initResult;
+ppResult->stmt = NULL;
+static int plannerLevel = 0;
+bool resourceNegotiateDone = false;
+QueryResource *savedQueryResource = GetActiveQueryResource();
+SetActiveRelType(NIL);
+
+bool isDispatchParallel = false;
+/*
+ * Before doing the true query optimization, we first run a 
resource_negotiator to give
+ * us some sense of the complexity of the query, and allocate the 
appropriate
+ * resource to run this query. After gaining the resource, we can 
perform the
+ * actual optimization.
+ */
+increase_planning_depth();
+
+plannerLevel++;
+if (!resourceNegotiateDone) {
+PG_TRY();
+{
--- End diff --

Indent here doesn't align. Please fix.


---
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-1516) add hawq start "userinput.ask_yesno"

[Xiang Sheng (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122752#comment-16122752
 ] 

Xiang Sheng commented on HAWQ-1516:
---

[~wangbincmss]
Could you comment your opinion about add the "ask_yesno" to "hawq start" ?  
Align to "hawq stop/init"  ? Or is there any other reasons ?

> add hawq start "userinput.ask_yesno" 
> -
>
> Key: HAWQ-1516
> URL: https://issues.apache.org/jira/browse/HAWQ-1516
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Command Line Tools
>Reporter: wangbincmss
>Assignee: Radar Lei
>Priority: Minor
>
> both  hawq  init and   hawq  stop  have "ask_yesno" ,   hawq  start  not  
> have "ask_yesno"
> "ask_yesno" will make users think twice for whether there is an alive cluster 
> and whether to proceed, I think   hawq  start should have "ask_yesno"  like 
> hawq  init and   hawq  stop



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HAWQ-1516) add hawq start "userinput.ask_yesno"

[wangbincmss (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wangbincmss updated HAWQ-1516:
--
Priority: Minor  (was: Major)

> add hawq start "userinput.ask_yesno" 
> -
>
> Key: HAWQ-1516
> URL: https://issues.apache.org/jira/browse/HAWQ-1516
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Command Line Tools
>Reporter: wangbincmss
>Assignee: Radar Lei
>Priority: Minor
>
> both  hawq  init and   hawq  stop  have "ask_yesno" ,   hawq  start  not  
> have "ask_yesno"
> "ask_yesno" will make users think twice for whether there is an alive cluster 
> and whether to proceed, I think   hawq  start should have "ask_yesno"  like 
> hawq  init and   hawq  stop



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HAWQ-1516) add hawq start "userinput.ask_yesno"

[wangbincmss (JIRA)]

wangbincmss created HAWQ-1516:
-

 Summary: add hawq start "userinput.ask_yesno" 
 Key: HAWQ-1516
 URL: https://issues.apache.org/jira/browse/HAWQ-1516
 Project: Apache HAWQ
  Issue Type: Improvement
  Components: Command Line Tools
Reporter: wangbincmss
Assignee: Radar Lei


both  hawq  init and   hawq  stop  have "ask_yesno" ,   hawq  start  not  have 
"ask_yesno"
"ask_yesno" will make users think twice for whether there is an alive cluster 
and whether to proceed, I think   hawq  start should have "ask_yesno"  like 
hawq  init and   hawq  stop



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-hawq issue #1279: HAWQ-1310. Reformat resource_negotiator().

[stanlyxiang]

Github user stanlyxiang commented on the issue:

https://github.com/apache/incubator-hawq/pull/1279
  
+1


---
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 #1279: HAWQ-1310. Reformat resource_negotiator().

[jiny2]

Github user jiny2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/1279
  
+1 LGTM. Thanks for fixing this so quickly.


---
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] [Resolved] (HAWQ-1511) Add TDE-related properties into hdfs-client.xml

[Amy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amy resolved HAWQ-1511.
---
Resolution: Fixed

> Add TDE-related properties into hdfs-client.xml
> ---
>
> Key: HAWQ-1511
> URL: https://issues.apache.org/jira/browse/HAWQ-1511
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: libhdfs
>Reporter: Hongxu Ma
>Assignee: Amy
> Fix For: 2.3.0.0-incubating
>
>
> include:
> * dfs.encryption.key.provider.uri
> * hadoop.security.crypto.buffer.size



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (HAWQ-1511) Add TDE-related properties into hdfs-client.xml

[Amy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amy closed HAWQ-1511.
-

> Add TDE-related properties into hdfs-client.xml
> ---
>
> Key: HAWQ-1511
> URL: https://issues.apache.org/jira/browse/HAWQ-1511
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: libhdfs
>Reporter: Hongxu Ma
>Assignee: Amy
> Fix For: 2.3.0.0-incubating
>
>
> include:
> * dfs.encryption.key.provider.uri
> * hadoop.security.crypto.buffer.size



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-hawq pull request #1279: HAWQ-1310. Reformat resource_negotiator()...

[amyrazz44]

GitHub user amyrazz44 opened a pull request:

https://github.com/apache/incubator-hawq/pull/1279

HAWQ-1310. Reformat resource_negotiator().

@jiny2 @linwen pls feel free to review this pull request, thank you.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/amyrazz44/incubator-hawq RM

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/1279.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 #1279


commit 2d98f0b3ae013a76a28f4c045a9e719eb1276d2e
Author: amyrazz44 
Date:   2017-08-09T02:57:14Z

HAWQ-1310. Reformat resource_negotiator().




---
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 #1276: HAWQ-1511. Add TDE-related properties int...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1276


---
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 #1275: HAWQ-1333. Change access mode of source f...

[amyrazz44]

Github user amyrazz44 closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1275


---
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 #1277: add hawq start "userinput.ask_yesno"

[wangbincmss]

Github user wangbincmss closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1277


---
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 #1277: add hawq start "userinput.ask_yesno"

[stanlyxiang]

Github user stanlyxiang commented on the issue:

https://github.com/apache/incubator-hawq/pull/1277
  
@wangbincmss  
Since hawq opened source and use apache JIRA to tracker all the changes, so 
for every pull request please create a apache jira first for your pull request 
like other PRs. Use the jira to describe your problem and devs can discuss 
whether we should do the changes under the jira.

For this pr, I don't think it's reasonable to add "userinput.ask_yesno" for 
"hawq start". IMO, "hawq init" or "hawq stop" will break the alive cluster if 
exists. "ask_yesno" will make users think twice for whether there is an alive 
cluster and whether to proceed. But there is no problem to proceed "hawq start" 
directly no matter how the cluster state is. "hawq start" will give 
corresponding hints for different errors.


---
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] [Updated] (HAWQ-1272) Modify code sample to use standard SQL syntax

[Yi Jin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Jin updated HAWQ-1272:
-
Fix Version/s: (was: 2.3.0.0-incubating)
   backlog

> Modify code sample to use standard SQL syntax
> -
>
> Key: HAWQ-1272
> URL: https://issues.apache.org/jira/browse/HAWQ-1272
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Jane Beckman
>Assignee: Radar Lei
> Fix For: backlog
>
>
> Parts of the code sample for checking table size should be uppercase.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HAWQ-1459) Tweak the feature test related entries in makefiles.

[Yi Jin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Jin updated HAWQ-1459:
-
Fix Version/s: (was: 2.3.0.0-incubating)
   backlog

> Tweak the feature test related entries in makefiles.
> 
>
> Key: HAWQ-1459
> URL: https://issues.apache.org/jira/browse/HAWQ-1459
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Paul Guo
>Assignee: Paul Guo
> Fix For: backlog
>
>
> We really do not need to set seperate entries for feature test in makefiles, 
> i.e.
> feature-test
> feature-test-clean
> This looks a bit ugly.
> Besides, in src/test/Makefile, there is typo, i.e.
> feature_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HAWQ-1147) Analyze will ERROR after register multiple parquet data files to a parquet table while enable debug and cassert in hawq configure

[Yi Jin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Jin updated HAWQ-1147:
-
Fix Version/s: (was: 2.3.0.0-incubating)
   backlog

> Analyze will ERROR after register multiple parquet data files to a parquet 
> table while enable debug and cassert in hawq configure
> -
>
> Key: HAWQ-1147
> URL: https://issues.apache.org/jira/browse/HAWQ-1147
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.1.0.0-incubating
>Reporter: Xiang Sheng
>Assignee: Xiang Sheng
> Fix For: backlog
>
>
> Enable debug and cassert in hawq configure, analyze will report Unexpected 
> internal error after register multiple parquet data files to the table. 
> reproduce steps:
> reproduce steps: 
> 1.  ./configure --enable-debug  --enable-cassert
> 2.  make -j8
> 3.  make install
> 4.  hawq init cluster -a
> 5.  hadoop fs -mkdir hdfs://localhost:8020/hawq_register_test
> 6.  hadoop fs -put 
> $hawq_home/src/test/feature/ManagementTool/test_hawq_register_hawq.paq 
> hdfs://localhost:8020/hawq_register_test/hawq1.paq
> 7.  create table t (i int) with (appendonly=true, orientation=parquet);
> 8.  hawq register -d postgres -f 
> hdfs://localhost:8020/hawq_register_test/hawq1.paq  t
> 9.  
> postgres=#  select oid from pg_class where relname = 't';
> oid
>+--+
>  24586
> (1 row)
> postgres=# select * from pg_aoseg.pg_paqseg_24586;
>  segno | eof | tupcount | eofuncompressed
> ---+-+--+-
>  1 | 657 |   -1 |  -1
> (1 rows)
> postgres=#analyze t;
> FATAL:  Unexpected internal error (analyze.c:1718)
> DETAIL:  FailedAssertion("!(relTuples > -1.0)", File: "analyze.c", Line: 1718)
> HINT:  Process 43356 will wait for gp_debug_linger=120 seconds before 
> termination.
> Note that its locks and other resources will not be released until then.
> server closed the connection unexpectedly
>   This probably means the server terminated abnormally
>   before or while processing the request.
> The connection to the server was lost. Attempting reset: Succeeded



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HAWQ-991) "HAWQ register" could register tables according to .yml configuration file

[Yi Jin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Jin updated HAWQ-991:

Fix Version/s: (was: 2.3.0.0-incubating)
   backlog

> "HAWQ register" could register tables according to .yml configuration file
> --
>
> Key: HAWQ-991
> URL: https://issues.apache.org/jira/browse/HAWQ-991
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Command Line Tools
>Affects Versions: 2.1.0.0-incubating
>Reporter: hongwu
>Assignee: hongwu
> Fix For: backlog
>
>
> Scenario: 
> 1. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
> data from Cluster A to Cluster B. Need Register data to Cluster B.
> 2. For the rollback of table. Do checkpoints somewhere, and need to rollback 
> to previous checkpoint. 
> Description:
> Register according to .yml configuration file. 
> hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
> config] [--force][--repair]  
> Behaviors:
> 1. If table doesn't exist, will automatically create the table and register 
> the files in .yml configuration file. Will use the filesize specified in .yml 
> to update the catalog table. 
> 2. If table already exist, and neither --force nor --repair configured. Do 
> not create any table, and directly register the files specified in .yml file 
> to the table. Note that if the file is under table directory in HDFS, will 
> throw error, say, to-be-registered files should not under the table path.
> 3. If table already exist, and --force is specified. Will clear all the 
> catalog contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, 
> and then re-register all the files to the table.  This is for scenario 2.
> 4. If table already exist, and --repair is specified. Will change both file 
> folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml 
> file configures. Note may some new generated files since the checkpoint may 
> be deleted here. Also note the all the files in .yml file should all under 
> the table folder on HDFS. Limitation: Do not support cases for hash table 
> redistribution, table truncate and table drop. This is for scenario 3.
> Requirements:
> 1. To be registered file path has to colocate with HAWQ in the same HDFS 
> cluster.
> 2. If to be registered is a hash table, the registered file number should be 
> one or multiple times or hash table bucket number.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HAWQ-916) Replace com.pivotal.hawq package name to org.apache.hawq

[Yi Jin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Jin updated HAWQ-916:

Fix Version/s: (was: 2.3.0.0-incubating)
   backlog

> Replace com.pivotal.hawq package name to org.apache.hawq
> 
>
> Key: HAWQ-916
> URL: https://issues.apache.org/jira/browse/HAWQ-916
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Storage
>Reporter: Lei Chang
>Assignee: Lei Chang
> Fix For: backlog
>
> Attachments: pivotal.txt
>
>
> com.pivotal.hawq.mapreduce types are referenced in at least the following 
> apache hawq (incubating) directories, master branch:
> contrib/hawq-hadoop
> contrib/hawq-hadoop/hawq-mapreduce-tool
> contrib/hawq-hadoop/hawq-mapreduce-parquet
> contrib/hawq-hadoop/hawq-mapreduce-common
> contrib/hawq-hadoop/hawq-mapreduce-ao
> contrib/hawq-hadoop/target/apidocs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-hawq issue #1278: HAWQ-1498. Segments keep open file descriptors f...

[jiny2]

Github user jiny2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/1278
  
I manually tested this fix in my environment, please review and comment.

@linwen @radarwave 


---
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 #1278: HAWQ-1498. Segments keep open file descri...

[jiny2]

GitHub user jiny2 opened a pull request:

https://github.com/apache/incubator-hawq/pull/1278

HAWQ-1498. Segments keep open file descriptors for deleted files

The idea is to hold a list of all connections ever used for dropping 
objects in HDFS, then when the transaction ends, no matter commit or rollback, 
those connections are forced to close. Those connections cached but never used 
for dropping, are not touched.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jiny2/incubator-hawq HAWQ-1498-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/1278.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 #1278


commit ad5d4d9995d8e47c863b3c532cee40166d790cf8
Author: Yi 
Date:   2017-08-10T09:15:06Z

HAWQ-1498. Segments keep open file descriptors for deleted files




---
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 #1275: HAWQ-1333. Change access mode of source files fo...

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/1275
  
+1


---
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 #1277: make hawq start cluster have "userinput.a...

[wangbincmss]

GitHub user wangbincmss opened a pull request:

https://github.com/apache/incubator-hawq/pull/1277

make hawq  start cluster  have "userinput.ask_yesno"  like  hawq stop 
cluster 

**The status quo:**
[hawqdb@docker1 bin]$ hawq start cluster
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Prepare to do 
'hawq start'
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-You can find log 
in:
    20170810:16:38:05:031474 
hawq_start:docker1:hawqdb-[INFO]:-/home/hawqdb/hawqAdminLogs/hawq_start_20170810.log
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-GPHOME is set to:
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-/home/hawqdb/hawq
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Start hawq with 
args: ['start', 'cluster']
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Gathering 
information and validating the environment...
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-No standby host 
configured
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Start all the 
nodes in hawq cluster
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Starting master 
node 'docker1.cmss.com'
    20170810:16:38:05:031474 hawq_start:docker1:hawqdb-[INFO]:-Start master 
service
    20170810:16:38:07:031474 hawq_start:docker1:hawqdb-[INFO]:-Master started 
successfully
    20170810:16:38:07:031474 hawq_start:docker1:hawqdb-[INFO]:-Start all the 
segments in hawq cluster
    20170810:16:38:07:031474 hawq_start:docker1:hawqdb-[INFO]:-Start segments 
in list: ['docker4.cmss.com', 'docker5.cmss.com', 'docker2.cmss.com', 
'docker3.cmss.com']
    20170810:16:38:07:031474 hawq_start:docker1:hawqdb-[INFO]:-Start segment 
service
    20170810:16:38:07:031474 hawq_start:docker1:hawqdb-[INFO]:-Total segment 
number is: 4
    
    20170810:16:38:11:031474 hawq_start:docker1:hawqdb-[INFO]:-4 of 4 segments 
start successfully
    20170810:16:38:11:031474 hawq_start:docker1:hawqdb-[INFO]:-Segments started 
successfully
    20170810:16:38:11:031474 hawq_start:docker1:hawqdb-[INFO]:-HAWQ cluster 
started successfully

[hawqdb@docker1 bin]$ hawq stop cluster
    20170810:16:47:24:003630 hawq_stop:docker1:hawqdb-[INFO]:-Prepare to do 
'hawq stop'
    20170810:16:47:24:003630 hawq_stop:docker1:hawqdb-[INFO]:-You can find log 
in:
    20170810:16:47:24:003630 
hawq_stop:docker1:hawqdb-[INFO]:-/home/hawqdb/hawqAdminLogs/hawq_stop_20170810.log
    20170810:16:47:24:003630 hawq_stop:docker1:hawqdb-[INFO]:-GPHOME is set to:
    20170810:16:47:24:003630 hawq_stop:docker1:hawqdb-[INFO]:-/home/hawqdb/hawq
    20170810:16:47:24:003630 hawq_stop:docker1:hawqdb-[INFO]:-Stop hawq with 
args: ['stop', 'cluster']

Continue with HAWQ service stop Yy|Nn (default=N):
    > y
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-No standby host 
configured
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-Stop hawq cluster
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-There are 0 
connections to the database
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-Commencing Master 
instance shutdown with mode='smart'
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-Master 
host=docker1.cmss.com
20170810:16:47:26:003630 hawq_stop:docker1:hawqdb-[INFO]:-Stop hawq master
20170810:16:47:27:003630 hawq_stop:docker1:hawqdb-[INFO]:-Master stopped 
successfully
20170810:16:47:27:003630 hawq_stop:docker1:hawqdb-[INFO]:-Stop hawq segment
20170810:16:47:27:003630 hawq_stop:docker1:hawqdb-[INFO]:-Stop segments in 
list: ['docker4.cmss.com', 'docker5.cmss.com', 'docker2.cmss.com', 
'docker3.cmss.com']
20170810:16:47:30:003630 hawq_stop:docker1:hawqdb-[INFO]:-Total segment 
number is: 4
...
20170810:16:47:33:003630 hawq_stop:docker1:hawqdb-[INFO]:-4 of 4 segments 
stop successfully
20170810:16:47:33:003630 hawq_stop:docker1:hawqdb-[INFO]:-Segments stopped 
successfully
20170810:16:47:33:003630 hawq_stop:docker1:hawqdb-[INFO]:-Cluster stopped 
successfully

**Ther ringht expale:**
[hawqdb@docker1 bin]$ hawq start  cluster
20170810:14:09:52:019805 hawq_start:docker1:hawqdb-[INFO]:-Prepare to do 
'hawq start'
20170810:14:09:52:019805 hawq_start:docker1:hawqdb-[INFO]:-You can find log 
in:
20170810:14:09:52:019805 
hawq_start:docker1:hawqdb-[INFO]:-/home/hawqdb/hawqAdminLogs/hawq_start_20170810.log
20170810:14:09:52:019805 hawq_start:docker1:hawqdb-[INFO]:-GPHOME is set to:
20170810:14:09:52:019805 hawq_start:docker1:hawqdb-[INFO]:-/home/hawqdb/hawq
20170810:14:09:52:019805 hawq_start:docker1:hawqdb-[INFO]:-Start hawq with 
args: ['start', 'cluster']

> 
> Continue with HAWQ service start Yy|Nn (default=N):
> > y

20170810:14:09:54:019805 hawq_start:docker1:hawqdb-[INFO]:-Gathering 
information and validating the environment...
20170810:14:09:54:

[GitHub] incubator-hawq issue #1275: HAWQ-1333. Change access mode of source files fo...

[jiny2]

Github user jiny2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/1275
  
Good job ! please have it delivered asap. Thanks.


---
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 #1275: HAWQ-1333. Change access mode of source files fo...

[jinyismilodon]

Github user jinyismilodon commented on the issue:

https://github.com/apache/incubator-hawq/pull/1275
  
Good job, please have pr delivered asap. Thanks.


---
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-1515) how to build and complie hawq based on suse11

[FengHuang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121108#comment-16121108
 ] 

FengHuang commented on HAWQ-1515:
-

yeah, if I finish it , I must try making some contributions to Wiki.

> how to build and complie hawq based on suse11
> -
>
> Key: HAWQ-1515
> URL: https://issues.apache.org/jira/browse/HAWQ-1515
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build
>Reporter: FengHuang
>Assignee: Radar Lei
>
> three are a little zypper rep for all kinds of dependencies for build of hawq 
> on suse11. can you recommend some available and comprehensive zypper rep?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)