Thanks. The logging exception is:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/lianjia/repo/hbaseWS/lib/phoenix-client.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/lianjia/.ivy2/cache/ch.qos.logback/logback-classic/jars/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
java.lang.ClassCastException: org.slf4j.impl.Log4jLoggerFactory cannot be
cast to ch.qos.logback.classic.LoggerContext
at
play.api.libs.logback.LogbackLoggerConfigurator.configure(LogbackLoggerConfigurator.scala:84)
at
play.api.libs.logback.LogbackLoggerConfigurator.configure(LogbackLoggerConfigurator.scala:66)
at
play.api.inject.guice.GuiceApplicationBuilder.$anonfun$configureLoggerFactory$1(GuiceApplicationBuilder.scala:122)
at scala.Option.map(Option.scala:146)
at
play.api.inject.guice.GuiceApplicationBuilder.configureLoggerFactory(GuiceApplicationBuilder.scala:121)
at
play.api.inject.guice.GuiceApplicationBuilder.applicationModule(GuiceApplicationBuilder.scala:100)
at
play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:185)
at
play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:137)
at
play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21)
at play.core.server.ProdServerStart$.start(ProdServerStart.scala:51)
at play.core.server.ProdServerStart$.main(ProdServerStart.scala:25)
at play.core.server.ProdServerStart.main(ProdServerStart.scala)
BTW, I am starting to look at https://hbase.apache.org/book.html#_rest
given that I cannot find a working phoenix client for play.
On Fri, Apr 20, 2018 at 7:04 PM, Sean Busbey <[email protected]> wrote:
> Hi!
>
> Are you subscribed to the user@hbase mailing list? Your original email
> has already gotten a reply:
>
> https://s.apache.org/z2iC
>
> On Fri, Apr 20, 2018 at 6:29 PM, Lian Jiang <[email protected]> wrote:
> > Any idea?
> >
> > phoenix-client.jar has multiple conflict with play, for example logback
> > v.s. log4j, guava 13 v.s. guava 22, etc.
> >
> > I don't see a way to handle this case and the ways I considered are:
> >
> > 1. shade phoenix-client.jar. I only see how to shade jars that available
> in
> > maven repository and did not see a way to shade a jar file.
> > 2. change the code in
> > https://github.com/apache/phoenix/tree/master/phoenix-client. It is
> > possible but looks like a lot of work to do.
> > 3. consider OSGI but playframework does not support it.
> >
> > Any clue is highly appreciated!
> >
> >
> > On Thu, Apr 19, 2018 at 10:56 AM, Lian Jiang <[email protected]>
> wrote:
> >
> >> I am using HDP 2.6 hbase and pheonix. I created a play rest service
> using
> >> hbase as the backend. However, I have trouble to get a working pheonix
> >> client.
> >>
> >> I tried the pheonix-client.jar given by HDP but its logging dependency
> >> conflicts with play's. Then I tried:
> >>
> >> libraryDependencies += "org.apache.phoenix" % "phoenix-core" %
> >> "4.13.1-HBase-1.1"
> >>
> >> libraryDependencies += "org.apache.phoenix" % "phoenix-server-client" %
> >> "4.7.0-HBase-1.1"
> >>
> >> libraryDependencies += "org.apache.phoenix" %
> "phoenix-queryserver-client"
> >> % "4.13.1-HBase-1.1"
> >>
> >> None of them worked: "No suitable driver found".
> >>
> >> Any idea will be highly appreciated!
> >>
>
>
>
> --
> Sean
>
