You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/02/01 07:28:34 UTC
[jira] [Commented] (PHOENIX-1613) Phoenix can't be used directly
with SquirrelSQL
[ https://issues.apache.org/jira/browse/PHOENIX-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300091#comment-14300091 ]
James Taylor commented on PHOENIX-1613:
---------------------------------------
+1. Thanks, [~gabriel.reid].
> 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, PHOENIX-1613b.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)