Github user pboado commented on the issue:
https://github.com/apache/phoenix/pull/286
Same patches here compressed into a .tar.gz file - easier to download -
[PR-286.tar.gz](https://github.com/apache/phoenix/files/1565194/PR-286.tar.gz)
---
Github user pboado commented on the issue:
https://github.com/apache/phoenix/pull/286
I think I found a way of applying the changes. I've just uploaded all files
generated by `git format-patch HEAD~14` to the JIRA ticket. By downloading them
into the same folders and running a `git
Github user pboado commented on the issue:
https://github.com/apache/phoenix/pull/286
Yes James, please revert the commit and I'll attach a set of patches to be
applied -almost all cherry picks applied with no conflicts-
---
Github user pboado commented on the issue:
https://github.com/apache/phoenix/pull/286
I don't really think it's a great idea squashing all commits for this PR,
it makes really difficult to track what has been merged and what hasn't from
master . Could you please reverse/rebase
GitHub user pboado opened a pull request:
https://github.com/apache/phoenix/pull/286
Sync 4.x-HBase-1.2 to master
This PR syncs 4.x-HBase-1.2 to master branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pboado/phoenix 4.x
Github user pboado closed the pull request at:
https://github.com/apache/phoenix/pull/285
---
GitHub user pboado opened a pull request:
https://github.com/apache/phoenix/pull/285
Sync 4.x-HBase-1.2 to master
This PR syncs 4.x-HBase-1.2 to master branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pboado/phoenix 4.x
