[
https://issues.apache.org/jira/browse/PHOENIX-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298318#comment-14298318
]
Gabriel Reid commented on PHOENIX-1613:
---------------------------------------
Yep, I'll put together a patch for this. My general idea was just to fully
disable metrics (and log a clear error) if initialization fails for any reason,
but I'll see if I can find a cleaner way of doing it somehow.
> 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)
