Hi again Nick so I applied your patch to the master and than copied phoenix_utils.py over to /bin folder with everything else from RC0 Original issue is fixed (thank you) but I have another one :) It still working thou but just throw exception when start (loooks like sqlline issue thou)
[******************* bin]# ./sqlline.py 172.16.251.78:2181:/hbase Setting property: [isolation, TRANSACTION_READ_COMMITTED] issuing: !connect jdbc:phoenix:****************:/hbase none none org.apache.phoenix.jdbc.PhoenixDriver Connecting to jdbc:phoenix:******************:/hbase SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 15/05/07 02:37:07 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Connected to: Phoenix (version 4.3) Driver: PhoenixEmbeddedDriver (version 4.3) Autocommit status: true Transaction isolation: TRANSACTION_READ_COMMITTED Building list of tables and columns for tab-completion (set fastconnect to true to skip)... 360/360 (100%) Done Done java.lang.NullPointerException at java.util.TreeMap.put(TreeMap.java:563) at java.util.TreeSet.add(TreeSet.java:255) at java.util.AbstractCollection.addAll(AbstractCollection.java:344) at java.util.TreeSet.addAll(TreeSet.java:312) at sqlline.SqlCompleter.<init>(SqlCompleter.java:81) at sqlline.DatabaseConnection.setCompletions(DatabaseConnection.java:84) at sqlline.SqlLine.setCompletions(SqlLine.java:1730) at sqlline.Commands.connect(Commands.java:1066) at sqlline.Commands.connect(Commands.java:996) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36) at sqlline.SqlLine.dispatch(SqlLine.java:804) at sqlline.SqlLine.initArgs(SqlLine.java:588) at sqlline.SqlLine.begin(SqlLine.java:656) at sqlline.SqlLine.start(SqlLine.java:398) at sqlline.SqlLine.main(SqlLine.java:292) sqlline version 1.1.8 I am also not sure why it shows connected to Phoenix 4.3 I guest because this (should it be changed or it changes when it become release?) ..\phoenix-4.4.0-HBase-0.98-src\phoenix-core\src\main\java\org\apache\phoenix\coprocessor\MetaDataProtocol.java public abstract class MetaDataProtocol extends MetaDataService { public static final int PHOENIX_MAJOR_VERSION = 4; public static final int PHOENIX_MINOR_VERSION = 3; On Wed, May 6, 2015 at 12:36 AM, Sergey Belousov <[email protected]> wrote: > thank you Nick > will check first thing in the morning > On May 5, 2015 10:56 PM, "Nick Dimiduk" <[email protected]> wrote: > >> Please have a look at https://issues.apache.org/jira/browse/PHOENIX-1948 >> >> On Tue, May 5, 2015 at 6:19 PM, [email protected] < >> [email protected]> wrote: >> >> > if scripts are not working as expected then let's sink the RC. >> > >> > Thanks, >> > Rajeshbabu. >> > >> > On Wed, May 6, 2015 at 6:32 AM, Nick Dimiduk <[email protected]> >> wrote: >> > >> >> This tgz layout looks consistent with previous. The trouble is >> >> bin/queryserver.py assumes the assembly tgz layout, not the make_rc.sh >> >> layout. Hence Sergey's original question. >> >> >> >> On Tue, May 5, 2015 at 6:00 PM, Enis Söztutar <[email protected]> >> wrote: >> >> >> >>> Just to be clear, >> >>> >> >>> I am saying that if the 4.4 RC tarball layout is the same/similar as >> the >> >>> previous RC layouts it is not a reason to sink the RC. But for >> future, we >> >>> should do the maven assemblies. >> >>> >> >>> Enis >> >>> >> >>> On Tue, May 5, 2015 at 4:53 PM, Enis Söztutar <[email protected]> >> >>> wrote: >> >>> >> >>> > I was inquiring the same thing in >> >>> > >> >>> >> https://issues.apache.org/jira/browse/PHOENIX-1945?focusedCommentId=14527077&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14527077 >> >>> > . >> >>> > >> >>> > I think we should get rid of the custom tarball format in >> >>> dev/make_rc.sh, >> >>> > and only do maven assembly packaging. Whether this sinks the RC is >> an >> >>> open >> >>> > question. The binary tarball is just for convenience actually. So I >> am >> >>> not >> >>> > sure we need to sink the RC as long as bigtop packaging can take >> this >> >>> > tarball and create the binary tarball in the expected layout. >> >>> > >> >>> > Enis >> >>> > >> >>> > On Tue, May 5, 2015 at 4:23 PM, Nick Dimiduk <[email protected]> >> >>> wrote: >> >>> > >> >>> >> Yeah, I just had a look at the content of the 4.4.0-bin RC. There's >> >>> no lib >> >>> >> folder, just jars in the top level. That's different from the >> bigtop >> >>> >> installation. This probably sinks the RC. >> >>> >> >> >>> >> + Rajesh >> >>> >> >> >>> >> On Tue, May 5, 2015 at 4:13 PM, Sergey Belousov < >> >>> >> [email protected]> >> >>> >> wrote: >> >>> >> >> >>> >> > I will try thank you >> >>> >> > my question was what would be proper (out of box) structure for >> the >> >>> >> > Phoenix client? >> >>> >> > >> >>> >> > in tar from what I remember it all jars together and than bin >> >>> folder. I >> >>> >> do >> >>> >> > not think it has lib folder unless assumption is that all jars >> >>> dumped to >> >>> >> > hbase/lib >> >>> >> > On May 5, 2015 6:47 PM, "Nick Dimiduk" <[email protected]> >> wrote: >> >>> >> > >> >>> >> > > Do try my suggestion on the ticket using the `touch` command to >> >>> create >> >>> >> > the >> >>> >> > > missing directory entry. It should fill in the gap for you. >> >>> >> > > >> >>> >> > > On Tue, May 5, 2015 at 3:39 PM, Sergey Belousov < >> >>> >> > [email protected] >> >>> >> > > > >> >>> >> > > wrote: >> >>> >> > > >> >>> >> > > > Thank you Nick >> >>> >> > > > I would not even call what we have packaging :) >> >>> >> > > > >> >>> >> > > > So what would be proper out of box folder structure for >> phoenix >> >>> 4.4 >> >>> >> > > client >> >>> >> > > > with sqlline ? >> >>> >> > > > >> >>> >> > > > we also switched to HDP 2.2 distribution if that make any >> >>> difference >> >>> >> > > > (hopefully not) >> >>> >> > > > >> >>> >> > > > thank you >> >>> >> > > > S >> >>> >> > > > On May 5, 2015 5:00 PM, "Nick Dimiduk" <[email protected]> >> >>> wrote: >> >>> >> > > > >> >>> >> > > > > Hi Sergey, >> >>> >> > > > > >> >>> >> > > > > Nice find. I left a comment over on PHOENIX-1904. From my >> >>> point of >> >>> >> > > view, >> >>> >> > > > > this is a bug raised by your custom packaging and not bad >> >>> enough >> >>> >> to >> >>> >> > > sink >> >>> >> > > > > the RC -- i.e., the RC should still work "out of the box". >> >>> Should >> >>> >> > > > > definitely file a ticket to make the launch scripts more >> >>> robust in >> >>> >> > the >> >>> >> > > > > future though! >> >>> >> > > > > >> >>> >> > > > > Thanks for spinning the bits. >> >>> >> > > > > -n >> >>> >> > > > > >> >>> >> > > > > On Tue, May 5, 2015 at 12:39 PM, Sergey Belousov < >> >>> >> > > > > [email protected]> >> >>> >> > > > > wrote: >> >>> >> > > > > >> >>> >> > > > > > Hello All >> >>> >> > > > > > >> >>> >> > > > > > I was trying 4.4 and came across following issue >> >>> >> > > > > > >> >>> >> > > > > > We had phoenix-client folder with phoenix-*-client.jar >> and >> >>> /bin >> >>> >> > > folder >> >>> >> > > > > > under. >> >>> >> > > > > > Than we used sqlline.py to run our schema creation >> scripts. >> >>> >> > > > > > After I updated bin folder from 4.4 and phoenix client >> with >> >>> >> > > > > > phoenix-4.4.0-HBase-0.98-client.jar when I try to run >> >>> sqlline.py >> >>> >> > > > > script.sql >> >>> >> > > > > > I am getting following errors: >> >>> >> > > > > > >> >>> >> > > > > > Applying _phoenixschema/001_.sql >> >>> >> > > > > > Traceback (most recent call last): >> >>> >> > > > > > File "phoenix-client/bin/psql.py", line 27, in <module> >> >>> >> > > > > > phoenix_utils.setPath() >> >>> >> > > > > > File "---/phoenix-client/bin/phoenix_utils.py", line >> 94, >> >>> in >> >>> >> > setPath >> >>> >> > > > > > phoenix_queryserver_jar = >> findFileInPathWithoutRecursion >> >>> >> > > > > > (PHOENIX_QUERYSERVER_JAR_PATTERN, >> os.path.join(current_dir, >> >>> >> "..", >> >>> >> > > > "lib")) >> >>> >> > > > > > File "---/phoenix-client/bin/phoenix_utils.py", line >> 45, >> >>> in >> >>> >> > > > > > findFileInPathWithoutRecursion >> >>> >> > > > > > files = [f for f in os.listdir(path) if >> >>> >> > > > os.path.isfile(os.path.join( >> >>> >> > > > > > path,f))] >> >>> >> > > > > > OSError: [Errno 2] No such file or directory: >> >>> >> > > > '---/phoenix-client/bin/../ >> >>> >> > > > > > lib' >> >>> >> > > > > > {noformat} >> >>> >> > > > > > >> >>> >> > > > > > >> >>> >> > > > > > Do I miss missing something (probably) ? >> >>> >> > > > > > What is the upgrade path from 4.3 to 4.4 >> >>> >> > > > > > Do I need to deploy >> >>> phoenix-server-4.4.0-HBase-0.98-runnable.jar >> >>> >> > on >> >>> >> > > > > server >> >>> >> > > > > > side even if I do not use query server yet ? >> >>> >> > > > > > >> >>> >> > > > > > I guess it related to >> >>> >> > > > https://issues.apache.org/jira/browse/PHOENIX-1904 >> >>> >> > > > > > >> >>> >> > > > > > I do not want to send it to phoenix 4.4 RC0 VOTE thread >> in a >> >>> >> hope >> >>> >> > it >> >>> >> > > > not >> >>> >> > > > > > problem with release by my hands :) >> >>> >> > > > > > >> >>> >> > > > > > Thank you, >> >>> >> > > > > > >> >>> >> > > > > >> >>> >> > > > >> >>> >> > > >> >>> >> > >> >>> >> >> >>> > >> >>> > >> >>> >> >> >> >> >> > >> >
