[jira] [Resolved] (HAWQ-1538) Install internal profiles definition file in conf directory

[Oleksandr Diachenko (JIRA)]

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

Oleksandr Diachenko resolved HAWQ-1538.
---
   Resolution: Fixed
Fix Version/s: 2.3.0.0-incubating

> Install internal profiles definition file in conf directory
> ---
>
> Key: HAWQ-1538
> URL: https://issues.apache.org/jira/browse/HAWQ-1538
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Ed Espino
> Fix For: 2.3.0.0-incubating
>
>
> As I user who installs PXF under some directory I want to have an empty file 
> installed under conf, which I can edit when I want to define my custom 
> profiles.



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

[GitHub] incubator-hawq issue #1300: HAWQ-1538. Install internal profiles definition ...

[sansanichfb]

Github user sansanichfb commented on the issue:

https://github.com/apache/incubator-hawq/pull/1300
  
@lavjain feel free to try it out by ```make install/tar/bundle 
DATABASE=gpdb```


---

[GitHub] incubator-hawq issue #1300: HAWQ-1538. Install internal profiles definition ...

[lavjain]

Github user lavjain commented on the issue:

https://github.com/apache/incubator-hawq/pull/1300
  
If the fix is working please feel free to merge. It is hard to review this 
kind of change.


---

[GitHub] incubator-hawq pull request #1300: HAWQ-1538. Install internal profiles defi...

[shivzone]

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

https://github.com/apache/incubator-hawq/pull/1300#discussion_r143605611
  
--- Diff: pxf/build.gradle ---
@@ -310,7 +309,7 @@ project('pxf-service') {
 }
 
 project.distTar {
-from('src/main/resources/pxf-profiles-default.xml') { into 'conf' 
rename { 'pxf-profiles.xml' } }
--- End diff --

Cool, as long as the above files exist with the right content we should be 
good


---

[GitHub] incubator-hawq pull request #1300: HAWQ-1538. Install internal profiles defi...

[shivzone]

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

https://github.com/apache/incubator-hawq/pull/1300#discussion_r143605252
  
--- Diff: pxf/build.gradle ---
@@ -310,7 +309,7 @@ project('pxf-service') {
 }
 
 project.distTar {
-from('src/main/resources/pxf-profiles-default.xml') { into 'conf' 
rename { 'pxf-profiles.xml' } }
--- End diff --

We might need both pxf-profile-default and pxf-profile in the tar


---

[GitHub] incubator-hawq pull request #1300: HAWQ-1538. Install internal profiles defi...

[sansanichfb]

GitHub user sansanichfb opened a pull request:

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

HAWQ-1538. Install internal profiles definition file in conf directory.



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

$ git pull https://github.com/sansanichfb/incubator-hawq HAWQ-1538

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

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


commit 2d36e1044ec715f790ce79c3db1e2881c8349bdc
Author: Oleksandr Diachenko 
Date:   2017-10-09T23:53:12Z

HAWQ-1538. Install internal profiles definition file in conf directory.




---

[jira] [Created] (HAWQ-1538) Install internal profiles definition file in conf directory

[Oleksandr Diachenko (JIRA)]

Oleksandr Diachenko created HAWQ-1538:
-

 Summary: Install internal profiles definition file in conf 
directory
 Key: HAWQ-1538
 URL: https://issues.apache.org/jira/browse/HAWQ-1538
 Project: Apache HAWQ
  Issue Type: Bug
  Components: PXF
Reporter: Oleksandr Diachenko
Assignee: Ed Espino


As I user who installs PXF under some directory I want to have an empty file 
installed under conf, which I can edit when I want to define my custom profiles.



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

[jira] [Resolved] (HAWQ-1537) Do not rely on listFiles' order in PartitionedJsonParserNoSeekTest

[Oleksandr Diachenko (JIRA)]

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

Oleksandr Diachenko resolved HAWQ-1537.
---
   Resolution: Fixed
Fix Version/s: 2.3.0.0-incubating

> Do not rely on listFiles' order in PartitionedJsonParserNoSeekTest
> --
>
> Key: HAWQ-1537
> URL: https://issues.apache.org/jira/browse/HAWQ-1537
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Ed Espino
> Fix For: 2.3.0.0-incubating
>
>
> Depending on a platform/Java version, order of listFiles could be different, 
> but this particular test - PartitionedJsonParserNoSeekTest, assumes that 
> listFiles returns files in alphabetical order which works on some platforms 
> and fails on another. 



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

[GitHub] incubator-hawq pull request #1299: HAWQ-1537. Sort files explicitly in Parti...

[sansanichfb]

Github user sansanichfb closed the pull request at:

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


---

[jira] [Commented] (HAWQ-1480) Packing a core file in hawq

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-1480:
--

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

https://github.com/apache/incubator-hawq-docs/pull/123#discussion_r143597015
  
--- Diff: book/master_middleman/source/subnavs/apache-hawq-nav.erb ---
@@ -117,6 +117,9 @@
   
 HAWQ 
Administrative Log Files
   
+  
+HAWQ packcore 
utility
--- End diff --

this is very minor - how about capitalizing the U in "utility"?


> Packing a core file in hawq
> ---
>
> Key: HAWQ-1480
> URL: https://issues.apache.org/jira/browse/HAWQ-1480
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Command Line Tools
>Reporter: Shubham Sharma
>Assignee: Radar Lei
> Fix For: 2.3.0.0-incubating
>
>
> Currently there is no way to packing a core file with its context – 
> executable, application and system shared libraries in hawq. This information 
> can be later unpacked on another system and helps in debugging. It is a 
> useful feature to quickly gather all the data needed from a crash/core 
> generated on the system to analyze it later.
> Another open source project, greenplum, uses a script 
> [https://github.com/greenplum-db/gpdb/blob/master/gpMgmt/sbin/packcore] to 
> collect this information. Tested this script against Hawq's installation and 
> it collects the required information needed for debug.
> Can this be merged into Hawq, if yes, I can submit a pull request and test it.



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

[jira] [Closed] (HAWQ-1536) pxf-json unit test failure due to json list comparison

[Shivram Mani (JIRA)]

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

Shivram Mani closed HAWQ-1536.
--

> pxf-json unit test failure due to json list comparison
> --
>
> Key: HAWQ-1536
> URL: https://issues.apache.org/jira/browse/HAWQ-1536
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Shivram Mani
>Assignee: Shivram Mani
> Fix For: backlog
>
>
> We see the following error while unit testing PXF JSON profile on certain 
> environments.
> {code}
> org.apache.hawq.pxf.plugins.json.parser.PartitionedJsonParserNoSeekTest > 
> testNoSeek FAILED
> org.junit.ComparisonFailure at PartitionedJsonParserNoSeekTest.java:71
> 16 tests completed, 1 failed
> :pxf-json:test FAILED
> {code}
> The reason for the failure is since the List of elements in the JSON data 
> seems to be different from the expected response. In non GCP environments the 
> parser always returned objects in the same order as it appeared in the RAW 
> JSON file. On the GCP environment that doesn't seem to be the case. This 
> could be related to the JVM version or the jackson library version.
> Will be fixing the unit test to not have any order order expectation in the 
> results returned



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

[jira] [Resolved] (HAWQ-1536) pxf-json unit test failure due to json list comparison

[Shivram Mani (JIRA)]

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

Shivram Mani resolved HAWQ-1536.

   Resolution: Duplicate
Fix Version/s: backlog

> pxf-json unit test failure due to json list comparison
> --
>
> Key: HAWQ-1536
> URL: https://issues.apache.org/jira/browse/HAWQ-1536
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Shivram Mani
>Assignee: Shivram Mani
> Fix For: backlog
>
>
> We see the following error while unit testing PXF JSON profile on certain 
> environments.
> {code}
> org.apache.hawq.pxf.plugins.json.parser.PartitionedJsonParserNoSeekTest > 
> testNoSeek FAILED
> org.junit.ComparisonFailure at PartitionedJsonParserNoSeekTest.java:71
> 16 tests completed, 1 failed
> :pxf-json:test FAILED
> {code}
> The reason for the failure is since the List of elements in the JSON data 
> seems to be different from the expected response. In non GCP environments the 
> parser always returned objects in the same order as it appeared in the RAW 
> JSON file. On the GCP environment that doesn't seem to be the case. This 
> could be related to the JVM version or the jackson library version.
> Will be fixing the unit test to not have any order order expectation in the 
> results returned



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

[GitHub] incubator-hawq pull request #1298: HAWQ-1536. Fix PXF Json no seek unit test

[shivzone]

Github user shivzone closed the pull request at:

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


---

[GitHub] incubator-hawq pull request #1299: HAWQ-1537. Sort files explicitly in Parti...

[sansanichfb]

GitHub user sansanichfb opened a pull request:

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

HAWQ-1537. Sort files explicitly in PartitionedJsonParserNoSeekTest.



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

$ git pull https://github.com/sansanichfb/incubator-hawq HAWQ-1537

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

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


commit f17e5a504edc58f5c6805f4cb192b155a6425612
Author: Oleksandr Diachenko 
Date:   2017-10-09T22:20:26Z

HAWQ-1537. Sort files explicitly in PartitionedJsonParserNoSeekTest.




---

[jira] [Created] (HAWQ-1537) Do not rely on listFiles' order in PartitionedJsonParserNoSeekTest

[Oleksandr Diachenko (JIRA)]

Oleksandr Diachenko created HAWQ-1537:
-

 Summary: Do not rely on listFiles' order in 
PartitionedJsonParserNoSeekTest
 Key: HAWQ-1537
 URL: https://issues.apache.org/jira/browse/HAWQ-1537
 Project: Apache HAWQ
  Issue Type: Bug
  Components: PXF
Reporter: Oleksandr Diachenko
Assignee: Ed Espino


Depending on a platform/Java version, order of listFiles could be different, 
but this particular test - PartitionedJsonParserNoSeekTest, assumes that 
listFiles returns files in alphabetical order which works on some platforms and 
fails on another. 



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

[GitHub] incubator-hawq pull request #1298: HAWQ-1536. Fix PXF Json no seek unit test

[shivzone]

GitHub user shivzone opened a pull request:

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

HAWQ-1536. Fix PXF Json no seek unit test

Fixed PartitionedJsonParserNoSeekTest to not have any expectation in 
expected response order.

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

$ git pull https://github.com/shivzone/incubator-hawq HAWQ-1536

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

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


commit fb59f5077a7d91dd7eebb23dae62eec4d71c4084
Author: shivzone 
Date:   2017-10-09T21:41:29Z

HAWQ-1536. Fix PXF Json no seek unit test




---

[jira] [Assigned] (HAWQ-1536) pxf-json unit test failure due to json list comparison

[Shivram Mani (JIRA)]

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

Shivram Mani reassigned HAWQ-1536:
--

Assignee: Shivram Mani  (was: Ed Espino)

> pxf-json unit test failure due to json list comparison
> --
>
> Key: HAWQ-1536
> URL: https://issues.apache.org/jira/browse/HAWQ-1536
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Shivram Mani
>Assignee: Shivram Mani
>
> We see the following error while unit testing PXF JSON profile on certain 
> environments.
> {code}
> org.apache.hawq.pxf.plugins.json.parser.PartitionedJsonParserNoSeekTest > 
> testNoSeek FAILED
> org.junit.ComparisonFailure at PartitionedJsonParserNoSeekTest.java:71
> 16 tests completed, 1 failed
> :pxf-json:test FAILED
> {code}
> The reason for the failure is since the List of elements in the JSON data 
> seems to be different from the expected response. In non GCP environments the 
> parser always returned objects in the same order as it appeared in the RAW 
> JSON file. On the GCP environment that doesn't seem to be the case. This 
> could be related to the JVM version or the jackson library version.
> Will be fixing the unit test to not have any order order expectation in the 
> results returned



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

[jira] [Created] (HAWQ-1536) pxf-json unit test failure due to json list comparison

[Shivram Mani (JIRA)]

Shivram Mani created HAWQ-1536:
--

 Summary: pxf-json unit test failure due to json list comparison
 Key: HAWQ-1536
 URL: https://issues.apache.org/jira/browse/HAWQ-1536
 Project: Apache HAWQ
  Issue Type: Bug
  Components: PXF
Reporter: Shivram Mani
Assignee: Ed Espino


We see the following error while unit testing PXF JSON profile on certain 
environments.
{code}
org.apache.hawq.pxf.plugins.json.parser.PartitionedJsonParserNoSeekTest > 
testNoSeek FAILED
org.junit.ComparisonFailure at PartitionedJsonParserNoSeekTest.java:71

16 tests completed, 1 failed
:pxf-json:test FAILED
{code}
The reason for the failure is since the List of elements in the JSON data seems 
to be different from the expected response. In non GCP environments the parser 
always returned objects in the same order as it appeared in the RAW JSON file. 
On the GCP environment that doesn't seem to be the case. This could be related 
to the JVM version or the jackson library version.

Will be fixing the unit test to not have any order order expectation in the 
results returned



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

[GitHub] incubator-hawq issue #1296: HAWQ-1496. Add DISCLAIMER, LICENSE and NOTICE fi...

[radarwave]

Github user radarwave commented on the issue:

https://github.com/apache/incubator-hawq/pull/1296
  
Seems this is only for pxf main rpm, how about the other rpms related to 
pxf?
pxf-hbase
pxf-hdfs
pxf-hive
pxf-jdbc
pxf-json
pxf-service


---

[jira] [Commented] (HAWQ-1416) hawq_toolkit administrative schema missing in HAWQ installation

[Radar Lei (JIRA)]

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

Radar Lei commented on HAWQ-1416:
-

hawq_toolkit administrative schema should be created while doing hawq master 
initialize. If the schema is not exist, then it should because the initialize 
process is failed to create hawq toolkit but not error out.

I verified the toolkit views exists without run "psql -f 
/usr/local/hawq/share/postgresql/gp_toolkit.sql". So I think this issue is 
fixed, we can have separate jira to track hawq_toolkit install failed issues if 
someone hit it.

> hawq_toolkit administrative schema missing in HAWQ installation
> ---
>
> Key: HAWQ-1416
> URL: https://issues.apache.org/jira/browse/HAWQ-1416
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools, DDL
>Reporter: Vineet Goel
>Assignee: Chunling Wang
> Fix For: 2.3.0.0-incubating
>
>
> hawq_toolkit administrative schema is not pre-installed with HAWQ, but should 
> actually be available once HAWQ is installed and initialized.
> Current workaround seems to be a manual command to install it:
> psql -f /usr/local/hawq/share/postgresql/gp_toolkit.sql



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