Nope, no worries there. I set up a 5.0.0-HBase-2.0 branch locally that
I'll rebase along the way. Thanks for checking though. I think any more
changes that land on 5.x will be a good thing.
On 2/8/18 2:26 AM, James Taylor wrote:
Josh - should we hold off check-ins to 5.x branch until the vote passes?
On Mon, Feb 5, 2018 at 4:30 PM, James Taylor <jamestay...@apache.org> wrote:
That list in the vote thread is good. IMHO, it'd be ok to add release
notes on the website once the vote passes. Couple of other minor features
I'm not sure about: Does atomic upsert work (UPSERT VALUES ... ON DUPLICATE
KEY ...)? Looks like point-in-time queries don't work correctly if your
table is taking writes (PHOENIX-4378).
One possible way to confirm any other missing feature would be to look at
newly ignored tests and any failing unit tests in 5.0.
On Mon, Feb 5, 2018 at 3:22 PM, Josh Elser <els...@apache.org> wrote:
Tried to include what I knew off the top of my head in the VOTE, but will
add it to the website if you think that will be helpful.
On 2/5/18 5:37 PM, James Taylor wrote:
Would be useful to write up release notes (typically here[1]) for what
doesn't work yet. I think this will help folks know what to test and not
test in the next RC.
[1] https://phoenix.apache.org/release_notes.html
On Mon, Feb 5, 2018 at 2:32 PM, Josh Elser <els...@apache.org> wrote:
Just put up a patch to 4582.
Any other comments from folks before I re-roll?
On 2/5/18 3:35 PM, James Taylor wrote:
-1. Need to fix PHOENIX-4582 or 4.x clients would attempt to connect to
5.x
server.
On Fri, Feb 2, 2018 at 8:45 PM, Artem Ervits <artemerv...@gmail.com>
wrote:
-1 (nonbinding)
md5 binary: OK
Centos 7.4
jdk: 1.8.0_161
hadoop 2.7.5
hbase 2.0
ran example
$PHOENIX_HOME/bin/psql.py localhost:2181:/hbase-unsecure
$PHOENIX_HOME/examples/WEB_STAT.sql $PHOENIX_HOME/examples/WEB_STA
T.csv
$PHOENIX_HOME/examples/WEB_STAT_QUERIES.sql
OK
ran example in https://phoenix.apache.org/Pho
enix-in-15-minutes-or-less.
html
OK
tried to run performance.py script
getting the same results as in
https://issues.apache.org/jira/browse/PHOENIX-4510
[vagrant@hadoop ~]$ $PHOENIX_HOME/bin/performance.py
localhost:2181:/hbase-unsecure 1000
Phoenix Performance Evaluation Script 1.0
-----------------------------------------
Creating performance table...
18/02/03 04:23:48 WARN util.NativeCodeLoader: Unable to load
native-hadoop
library for your platform... using builtin-java classes where
applicable
no rows upserted
Time: 4.59 sec(s)
Query # 1 - Count - SELECT COUNT(1) FROM PERFORMANCE_1000;
Query # 2 - Group By First PK - SELECT HOST FROM PERFORMANCE_1000
GROUP
BY
HOST;
Query # 3 - Group By Second PK - SELECT DOMAIN FROM PERFORMANCE_1000
GROUP
BY DOMAIN;
Query # 4 - Truncate + Group By - SELECT TRUNC(DATE,'DAY') DAY FROM
PERFORMANCE_1000 GROUP BY TRUNC(DATE,'DAY');
Query # 5 - Filter + Count - SELECT COUNT(1) FROM PERFORMANCE_1000
WHERE
CORE<10;
Generating and upserting data...
Error: Invalid or corrupt jarfile /tmp/data_akuell.csv
NOT OK
sqlline still shows version 4.13
Connected to: Phoenix (version 4.13)
Driver: PhoenixEmbeddedDriver (version 4.13)
NOT OK
On Fri, Feb 2, 2018 at 10:58 AM, Josh Elser <els...@apache.org>
wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc0. This
release
is only targeting Apache HBase 2.0 and is known to have lacking
functionality as compared to previous releases (e.g. transactional
tables,
Hive integration, full local indexing support). It is presented as-is
in
an
attempt to encourage the community at large to get involved.
The RC is available at the standard location:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
x-5.0.0-alpha-HBase-2.0-rc0
RC0 is based on the following commit: a2053c1d3b64a9cc2f35b1f83faa54
e421bb20f1
Signed with my key: 9E62822F4668F17B0972ADD9B7D5CD454677D66C,
http://pgp.mit.edu/pks/lookup?op=get&search=0xB7D5CD454677D66C
Vote will be open for at least 72 hours (2018/02/05 1600GMT). Please
vote:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
Thanks,
The Apache Phoenix Team
