You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by xinzweb <gi...@git.apache.org> on 2015/12/11 03:04:14 UTC
[GitHub] incubator-hawq pull request: Move ivy.xml for qpopt inside apache-...
GitHub user xinzweb opened a pull request:
https://github.com/apache/incubator-hawq/pull/182
Move ivy.xml for qpopt inside apache-hawq for better dependency management
This is part 1 of 2 step check-in to have better way managing dependencies between HAWQ and optimizer.
Originally, we have ivy.xml managed separately from apache-hawq, and caused inconsistency between HAWQ and optimizer components.
With this fix, we can change the dependency the same time we change the HAWQ code, hence reduce failures due to inconsistent dependencies.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xinzweb/incubator-hawq master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/182.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 #182
----
commit 219dd0593e5080e244c71a7aa66ddd8b4d8cc189
Author: Xin Zhang <xz...@pivotal.io>
Date: 2015-12-11T02:00:32Z
Move ivy.xml for qpopt inside apache-hawq for better dependency management
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: Move ivy.xml for qpopt inside apache-...
Posted by wangzw <gi...@git.apache.org>.
Github user wangzw commented on the pull request:
https://github.com/apache/incubator-hawq/pull/182#issuecomment-163883800
looks good to me. +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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: Move ivy.xml for qpopt inside apache-...
Posted by entong <gi...@git.apache.org>.
Github user entong commented on the pull request:
https://github.com/apache/incubator-hawq/pull/182#issuecomment-163816579
@wangzw We are bringing the ivy settings related to Orca inside apache, since the translator changes and version update always go hand in hand. By doing so we don't need to push to both repos for every refresh of Orca. Saves us tons of time.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: Move ivy.xml for qpopt inside apache-...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-hawq/pull/182
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: Move ivy.xml for qpopt inside apache-...
Posted by entong <gi...@git.apache.org>.
Github user entong commented on the pull request:
https://github.com/apache/incubator-hawq/pull/182#issuecomment-164004394
Thanks! This is a small step on the way to open source Orca.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---