[
https://issues.apache.org/jira/browse/PHOENIX-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1613:
----------------------------------
Attachment: PHOENIX-1613.patch
Copy/paste of v 3.2.1 commons collections dependencies into phoenix-core.
Probably a bad idea, though, as there'll likely be class overlaps that lead to
issues. First batch of tests seem to pass, but I'm running into an issue later.
Maybe another ideas, more promising would be to have phoenix client depend
still on 2.1 commons collections with phoenix server depending on 3.2.1, as the
dependencies seem to be server side?
> Phoenix can't be used directly with SquirrelSQL
> -----------------------------------------------
>
> Key: PHOENIX-1613
> URL: https://issues.apache.org/jira/browse/PHOENIX-1613
> Project: Phoenix
> Issue Type: Bug
> Reporter: Gabriel Reid
> Attachments: PHOENIX-1613.patch
>
>
> Due to an conflicting versions of (at least) commons-collections, Phoenix no
> longer works with [SquirrelSQL|http://squirrel-sql.sourceforge.net]. The
> error that is given is the following:
> {code}
> java.lang.IllegalAccessError: class
> org.apache.commons.collections.iterators.EmptyOrderedIterator cannot access
> its superclass
> org.apache.commons.collections.iterators.AbstractEmptyIterator
> {code}
> SquirrelSQL apparently uses commons-collections 2.x, while Phoenix uses
> commons-collections 3.2.1.
> It's not totally clear what can be done to resolve this. It wasn't previously
> an issue, so there is a specific piece of code (apparently related to
> tracing) that now tickles this incompatibility. Probably the easiest fix is
> to get SquirrelSQL to upgrade to a more recent version of
> commons-collections, although there may be other ways to resolve this.
> This issue has already been reported as-is to the SquirrelSQL project:
> http://sourceforge.net/p/squirrel-sql/mailman/message/33039278/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
