[GitHub] incubator-hawq pull request #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119750193 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -111,30 +110,40 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { partitionBy = inConf.getUserProperty("PARTITION_BY").split(":"); partitionColumn = partitionBy[0]; partitionType = PartitionType.getType(partitionBy[1]); -} catch (IllegalArgumentException e1) { +} catch (IllegalArgumentException | ArrayIndexOutOfBoundsException e1) { throw new UserDataException("The parameter 'PARTITION_BY' invalid, the pattern is 'column_name:date|int|enum'"); } +//parse and validate parameter-RANGE try { -range = inConf.getUserProperty("RANGE").split(":"); +if (inConf.getUserProperty("RANGE") != null) { +range = inConf.getUserProperty("RANGE").split(":"); +if (range.length == 1 && partitionType != PartitionType.ENUM) +throw new UserDataException("The parameter 'RANGE' does not specify '[:end_value]'"); --- End diff -- in the similar fashion, we might support open ended lower range as well -- in cases where min value is not known or changes dynamically. --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user sansanichfb commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119746963 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -111,30 +110,40 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { partitionBy = inConf.getUserProperty("PARTITION_BY").split(":"); partitionColumn = partitionBy[0]; partitionType = PartitionType.getType(partitionBy[1]); -} catch (IllegalArgumentException e1) { +} catch (IllegalArgumentException | ArrayIndexOutOfBoundsException e1) { throw new UserDataException("The parameter 'PARTITION_BY' invalid, the pattern is 'column_name:date|int|enum'"); } +//parse and validate parameter-RANGE try { -range = inConf.getUserProperty("RANGE").split(":"); +if (inConf.getUserProperty("RANGE") != null) { +range = inConf.getUserProperty("RANGE").split(":"); +if (range.length == 1 && partitionType != PartitionType.ENUM) +throw new UserDataException("The parameter 'RANGE' does not specify '[:end_value]'"); --- End diff -- If we want to support open-ended range on fragmenter phase - we might have the last fragment having more data than rest of fragments, which is acceptable and very user-friendly so +1 for having open-ended range. --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119738385 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -111,30 +110,40 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { partitionBy = inConf.getUserProperty("PARTITION_BY").split(":"); partitionColumn = partitionBy[0]; partitionType = PartitionType.getType(partitionBy[1]); -} catch (IllegalArgumentException e1) { +} catch (IllegalArgumentException | ArrayIndexOutOfBoundsException e1) { throw new UserDataException("The parameter 'PARTITION_BY' invalid, the pattern is 'column_name:date|int|enum'"); } +//parse and validate parameter-RANGE try { -range = inConf.getUserProperty("RANGE").split(":"); +if (inConf.getUserProperty("RANGE") != null) { --- End diff -- "RANGE" should be an enum value or at least a constant somewhere --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119739575 --- Diff: pxf/pxf-jdbc/src/test/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenterTest.java --- @@ -164,8 +163,8 @@ public void inValidParameterFormat() throws Exception { when(inputData.getUserProperty("RANGE")).thenReturn("100:200"); try { new JdbcPartitionFragmenter(inputData); -fail("Expected an ArrayIndexOutOfBoundsException"); -} catch (ArrayIndexOutOfBoundsException ex) { +fail("Expected an UserDataException"); --- End diff -- use @Test(expected = UserDataException.class) so that there is no need for try / catch / fail lines : https://github.com/junit-team/junit4/wiki/exception-testing --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119740279 --- Diff: pxf/build.gradle --- @@ -111,6 +111,10 @@ subprojects { subProject -> force 'org.codehaus.jackson:jackson-mapper-asl:1.9.13' force 'junit:junit:4.11' } +configurations { +exclude group: 'org.json', module: 'json' --- End diff -- are we sure it will run OK without it ? --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119738227 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -111,30 +110,40 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { partitionBy = inConf.getUserProperty("PARTITION_BY").split(":"); partitionColumn = partitionBy[0]; partitionType = PartitionType.getType(partitionBy[1]); -} catch (IllegalArgumentException e1) { +} catch (IllegalArgumentException | ArrayIndexOutOfBoundsException e1) { throw new UserDataException("The parameter 'PARTITION_BY' invalid, the pattern is 'column_name:date|int|enum'"); } +//parse and validate parameter-RANGE try { -range = inConf.getUserProperty("RANGE").split(":"); +if (inConf.getUserProperty("RANGE") != null) { +range = inConf.getUserProperty("RANGE").split(":"); --- End diff -- calling same function twice, would be better to call it once saving result and then using the result for further logic --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119739058 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -144,7 +153,7 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { rangeEnd.setTime(df.parse(range[1])); } } catch (ParseException e) { -throw new UserDataException("The parameter 'RANGE' include invalid date format."); +throw new UserDataException("The parameter 'RANGE' has invalid date format."); --- End diff -- should we also say what expected format is, such as : "-MM-dd" ? --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119740046 --- Diff: pxf/pxf-jdbc/src/test/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenterTest.java --- @@ -211,6 +210,90 @@ public void inValidIntervaltype() throws Exception { } @Test +public void testIntervaltypeMissing() throws Exception { +prepareConstruction(); +when(inputData.getDataSource()).thenReturn("sales"); + when(inputData.getUserProperty("PARTITION_BY")).thenReturn("cdate:date"); + when(inputData.getUserProperty("RANGE")).thenReturn("2008-01-01:2011-01-01"); +when(inputData.getUserProperty("INTERVAL")).thenReturn("6"); + +try { +JdbcPartitionFragmenter fragment = new JdbcPartitionFragmenter(inputData); +fragment.getFragments(); +fail("Expected an UserDataException"); +} catch (UserDataException ex) { +} +} + +@Test +public void testIntervaltypeMissingValid() throws Exception { +prepareConstruction(); +when(inputData.getDataSource()).thenReturn("sales"); + when(inputData.getUserProperty("PARTITION_BY")).thenReturn("year:int"); +when(inputData.getUserProperty("RANGE")).thenReturn("2001:2012"); +when(inputData.getUserProperty("INTERVAL")).thenReturn("1"); + +JdbcPartitionFragmenter fragment = new JdbcPartitionFragmenter(inputData); +List fragments = fragment.getFragments(); +assertEquals(fragments.size(), 11); --- End diff -- the order of params for assertEquals usually goes (expected, actual) : http://junit.sourceforge.net/javadoc/org/junit/Assert.html#assertEquals(java.lang.Object, java.lang.Object) as it will report errors as such, so it might be confusing when error happens what was actually expected and what was returned. --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119738672 --- Diff: pxf/pxf-jdbc/src/main/java/org/apache/hawq/pxf/plugins/jdbc/JdbcPartitionFragmenter.java --- @@ -111,30 +110,40 @@ public JdbcPartitionFragmenter(InputData inConf) throws UserDataException { partitionBy = inConf.getUserProperty("PARTITION_BY").split(":"); partitionColumn = partitionBy[0]; partitionType = PartitionType.getType(partitionBy[1]); -} catch (IllegalArgumentException e1) { +} catch (IllegalArgumentException | ArrayIndexOutOfBoundsException e1) { throw new UserDataException("The parameter 'PARTITION_BY' invalid, the pattern is 'column_name:date|int|enum'"); } +//parse and validate parameter-RANGE try { -range = inConf.getUserProperty("RANGE").split(":"); +if (inConf.getUserProperty("RANGE") != null) { +range = inConf.getUserProperty("RANGE").split(":"); +if (range.length == 1 && partitionType != PartitionType.ENUM) +throw new UserDataException("The parameter 'RANGE' does not specify '[:end_value]'"); --- End diff -- why did we drop support for open-ended range ? --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user sansanichfb commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119723516 --- Diff: pxf/pxf-api/src/main/java/org/apache/hawq/pxf/api/StatsAccessor.java --- @@ -29,11 +29,13 @@ /** * Method which reads needed statistics for current split + * @throws Exception if retrieving the stats failed */ public void retrieveStats() throws Exception; /** * Returns next tuple based on statistics information without actual reading of data + * @return only one row --- End diff -- @return next row without reading it from disk --- 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 #1249: HAWQ-1461. Improve partition parameters v...
Github user sansanichfb commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1249#discussion_r119723348 --- Diff: pxf/build.gradle --- @@ -477,7 +481,7 @@ def buildNumber() { } task wrapper(type: Wrapper) { -gradleVersion = '2.11' +gradleVersion = '2.14.1' --- End diff -- Why do we need to update Gradle version? --- 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 #1249: HAWQ-1461. Improve partition parameters v...
GitHub user lavjain opened a pull request: https://github.com/apache/incubator-hawq/pull/1249 HAWQ-1461. Improve partition parameters validation for PXF-JDBC plugin You can merge this pull request into a Git repository by running: $ git pull https://github.com/lavjain/incubator-hawq master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1249.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 #1249 commit 2c435cd87f13a3308b1e61f8e85fb6989f3cd7c0 Author: lavjainDate: 2017-05-26T18:28:48Z HAWQ-1461. Improve partition parameters validation for PXF-JDBC plugin --- 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-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen resolved HAWQ-1473. - Resolution: Fixed Fix Version/s: 2.3.0.0-incubating PR accepted; resolving and closing. > document ranger plug-in service high availability > - > > Key: HAWQ-1473 > URL: https://issues.apache.org/jira/browse/HAWQ-1473 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie > Fix For: 2.3.0.0-incubating > > > add RPS high availability information to the docs. include config info as > well as failover scenarios. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033384#comment-16033384 ] ASF GitHub Bot commented on HAWQ-1473: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/120 > document ranger plug-in service high availability > - > > Key: HAWQ-1473 > URL: https://issues.apache.org/jira/browse/HAWQ-1473 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie > > add RPS high availability information to the docs. include config info as > well as failover scenarios. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1245: HAWQ-1476. Augment enable-ranger-plugin.s...
Github user denalex commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1245#discussion_r119684260 --- Diff: ranger-plugin/conf/ranger-servicedef-hawq.json --- @@ -244,7 +244,7 @@ "name": "authentication", "type": "enum", "subType": "authType", - "mandatory": false, + "mandatory": true, --- End diff -- We have decided a while ago to not touch pg_hba.conf in Ambari, because users might have their own entries there and this is a very sensitive file. A viable approach might've been to manage all entries in pg_hba.conf via Ambari, but that required extra work. --- 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] [Created] (HAWQ-1479) document hawq/ranger kerberos support
Lisa Owen created HAWQ-1479: --- Summary: document hawq/ranger kerberos support Key: HAWQ-1479 URL: https://issues.apache.org/jira/browse/HAWQ-1479 Project: Apache HAWQ Issue Type: Improvement Components: Documentation Reporter: Lisa Owen Assignee: David Yozie add some doc content addressing hawq/ranger/rps kerberos config and any other considerations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1248: HAWQ-1476. Augment enable-ranger-plugin.s...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/1248 --- 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 #1248: HAWQ-1476. Augment enable-ranger-plugin.sh to su...
Github user paul-guo- commented on the issue: https://github.com/apache/incubator-hawq/pull/1248 +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 #1248: HAWQ-1476. Augment enable-ranger-plugin.s...
GitHub user stanlyxiang opened a pull request: https://github.com/apache/incubator-hawq/pull/1248 HAWQ-1476. Augment enable-ranger-plugin.sh to support kerberos. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stanlyxiang/incubator-hawq HAWQ-1476 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1248.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 #1248 commit 4cddcdea2b54b11ffb6d1fe63b64c3b0f96a0b57 Author: stanlyxiangDate: 2017-06-01T07:41:55Z HAWQ-1476. Augment enable-ranger-plugin.sh to support kerberos. --- 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 #1245: HAWQ-1476. Augment enable-ranger-plugin.s...
Github user ictmalili commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1245#discussion_r119541625 --- Diff: ranger-plugin/scripts/enable-ranger-plugin.sh --- @@ -20,7 +20,7 @@ # function usage() { - echo "USAGE: enable-ranger-plugin.sh -r ranger_host:ranger_port -u ranger_user -p ranger_password [-h hawq_host:hawq_port] -w hawq_user -q hawq_password" + echo "USAGE: enable-ranger-plugin.sh -r ranger_host:ranger_port -u ranger_user -p ranger_password [-h hawq_host:hawq_port -c hawq_kerberos_service_name] -w hawq_user -q hawq_password -t lookup_authentication_type" exit 1 } --- End diff -- I think "-t lookup_authentication_type" should be moved in front of "-c hawq_kerberos_service_name", and should also be marked as optional with default value "simple". "-c hawq_kerberos_service_name" can be changed to "-s", since it indicates the service name. --- 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-1478) Enable hawq build on suse11
[ https://issues.apache.org/jira/browse/HAWQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Guo resolved HAWQ-1478. Resolution: Fixed > Enable hawq build on suse11 > --- > > Key: HAWQ-1478 > URL: https://issues.apache.org/jira/browse/HAWQ-1478 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Affects Versions: 2.2.0.0-incubating >Reporter: Paul Guo >Assignee: Radar Lei > Fix For: 2.3.0.0-incubating > > > We have some users want hawq run on suse (typically suse11). We have at first > make it build fine on the platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1247: HAWQ-1478. Enable hawq build on suse11
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/1247 --- 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 #1245: HAWQ-1476. Augment enable-ranger-plugin.sh to su...
Github user ictmalili commented on the issue: https://github.com/apache/incubator-hawq/pull/1245 LGTM. +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 #1247: HAWQ-1478. Enable hawq build on suse11
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/1247 LGTM +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 #1247: HAWQ-1478. Enable hawq build on suse11
GitHub user paul-guo- opened a pull request: https://github.com/apache/incubator-hawq/pull/1247 HAWQ-1478. Enable hawq build on suse11 This was done by amyrazz44, edespino, internma and liming01 intermittently. You can merge this pull request into a Git repository by running: $ git pull https://github.com/paul-guo-/incubator-hawq make Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1247.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 #1247 commit abd74ed1cc6a1df538ea5ac9df4bef5ce6b52c29 Author: intermaDate: 2017-04-25T07:35:36Z HAWQ-1478. Enable hawq build on suse11 This was done by amyrazz44, edespino, internma and liming01 intermittently. --- 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-1478) Enable hawq build on suse11
[ https://issues.apache.org/jira/browse/HAWQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-1478: Fix Version/s: 2.3.0.0-incubating > Enable hawq build on suse11 > --- > > Key: HAWQ-1478 > URL: https://issues.apache.org/jira/browse/HAWQ-1478 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Affects Versions: 2.2.0.0-incubating >Reporter: Paul Guo >Assignee: Radar Lei > Fix For: 2.3.0.0-incubating > > > We have some users want hawq run on suse (typically suse11). We have at first > make it build fine on the platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HAWQ-1478) Enable hawq build on suse11
[ https://issues.apache.org/jira/browse/HAWQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-1478: Affects Version/s: 2.2.0.0-incubating > Enable hawq build on suse11 > --- > > Key: HAWQ-1478 > URL: https://issues.apache.org/jira/browse/HAWQ-1478 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Affects Versions: 2.2.0.0-incubating >Reporter: Paul Guo >Assignee: Radar Lei > Fix For: 2.3.0.0-incubating > > > We have some users want hawq run on suse (typically suse11). We have at first > make it build fine on the platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HAWQ-1478) Enable hawq build on suse11
[ https://issues.apache.org/jira/browse/HAWQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-1478: Component/s: Build > Enable hawq build on suse11 > --- > > Key: HAWQ-1478 > URL: https://issues.apache.org/jira/browse/HAWQ-1478 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Affects Versions: 2.2.0.0-incubating >Reporter: Paul Guo >Assignee: Radar Lei > Fix For: 2.3.0.0-incubating > > > We have some users want hawq run on suse (typically suse11). We have at first > make it build fine on the platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HAWQ-1478) Enable hawq build on suse11
Paul Guo created HAWQ-1478: -- Summary: Enable hawq build on suse11 Key: HAWQ-1478 URL: https://issues.apache.org/jira/browse/HAWQ-1478 Project: Apache HAWQ Issue Type: Bug Reporter: Paul Guo Assignee: Radar Lei We have some users want hawq run on suse (typically suse11). We have at first make it build fine on the platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)