Re: Almost ready for HBaseCon+PhoenixCon 2018 SanJose CFP

On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser <els...@apache.org> wrote: > > > On 3/21/18 2:59 AM, Stack wrote: > >> On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser <els...@apache.org> wrote: >> >> Hi all, >>> >>> I've published a new websi

Re: Almost ready for HBaseCon+PhoenixCon 2018 SanJose CFP

On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote: > Hi all, > > I've published a new website for the upcoming event in June in California > at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are > identical. > > I've not yet updated any links on either website

[RESULT][VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

of course [1]. St.Ack 1. In case it not plain, we are trying to stabilize branch-2. Care needs to be exercised backporting. Bug fixes only please. If in doubt, ping me, the RM, please. Thanks. On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote: > The first release

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

he cluster. It shouldn't. Let me try it myself. If I can't repro the damage I'll come looking for you. Thanks JMS, S > JMS > > 2018-01-03 22:26 GMT-05:00 Stack <st...@duboce.net>: > > > +1 from me. > > S > > > > On Fri, Dec 29, 2017 at 12:15 PM, Stack <st..

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

+1 from me. S On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote: > The first release candidate for HBase 2.0.0-beta-1 is up at: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/ > > Maven artifacts are available from a staging direc

[jira] [Commented] (PHOENIX-4459) Region assignments are failing for the test cases with extended clocks to support SCN

[ https://issues.apache.org/jira/browse/PHOENIX-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309839#comment-16309839 ] stack commented on PHOENIX-4459: I commented up on dev list. I am away from a computer but stalling

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

There is nothing further up in the master log from regionservers or on regionservers side on open? Thanks, S On Dec 31, 2017 8:37 AM, "stack" <saint@gmail.com> wrote: > Good questions. If you disable snappy does it work? If you start over > fresh does it work? I

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Good questions. If you disable snappy does it work? If you start over fresh does it work? It should be picking up native libs. Make an issue please jms. Thanks for giving it a go. S On Dec 30, 2017 11:49 PM, "Jean-Marc Spaggiari" <jean-m...@spaggiari.org> wrote: > H

[VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

The first release candidate for HBase 2.0.0-beta-1 is up at: https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/ Maven artifacts are available from a staging directory here: https://repository.apache.org/content/repositories/orgapachehbase-1188 All was signed with my key at

[VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

The first release candidate for HBase 2.0.0-alpha4 is up at: https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/ Maven artifacts are available from a staging directory here: https://repository.apache.org/content/repositories/orgapachehbase-1178 All was signed with my key at

Re: [DISCUSS] Road to HBase 2.0.0

On Wed, Oct 18, 2017 at 12:13 PM, Josh Elser wrote: > > On 10/18/17 2:51 PM, Andrew Purtell wrote: > >> Hopefully, Phoenix will not find itself in a position where >>> >> business-critical things it's doing are being removed from API (and >> Phoenix >> has no recourse to hack

Re: [DISCUSS] Road to HBase 2.0.0

Some notes on this effort: + Perhaps this discussion should be cc'd to dev@hbase? There is a good bit of overlap between dev-set here and dev-set on hbase and some interest/concern around Phoenix on HBase2. + Here are some notes I took after looking at Phoenix last week that I ran by James

Re: [VOTE] First hbase-2.0.0-alpha-3 Release Candidate is available

.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain( > AbstractHBaseTool.java:262) > at > org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:793) > > On Fri, Sep 15, 2017 at 11:03 AM, Stack <st...@duboce.net> wrote: >

[VOTE] First hbase-2.0.0-alpha-3 Release Candidate is available

The first release candidate for HBase 2.0.0-alpha-3 is up at: https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-3RC0/ Maven artifacts are available from a staging directory here: https://repository.apache.org/content/repositories/orgapachehbase-1175 All was signed with my key

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166789#comment-16166789 ] stack commented on PHOENIX-3111: Funny. I took a look at HBASE-14893. My comment on it (ignored

FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2

Projects like Phoenix could run would their own versions of libs thereafter (but would no longer be able to depend nor transitively include from hbase). Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if interested/concerned. Thanks, St.Ack

Is HBASE-17716 needed in an hbase-1.3 release?

Please comment over in HBASE-17886 whether or which. Thanks, St.Ack

Re: Issues while Running Apache Phoenix against TPC-H data

On Fri, Aug 19, 2016 at 1:19 PM, James Taylor <jamestay...@apache.org> wrote: > On Fri, Aug 19, 2016 at 11:37 AM, Stack <st...@duboce.net> wrote: > > > On Thu, Aug 18, 2016 at 5:54 PM, James Taylor <jamestay...@apache.org> > > wrote: > > > >

Re: Issues while Running Apache Phoenix against TPC-H data

asis verifying no regression in performance or in utility. Thanks, St.Ack > Thanks, > James > > On Thu, Aug 18, 2016 at 5:36 PM, Stack <st...@duboce.net> wrote: > > > On Thu, Aug 18, 2016 at 3:00 PM, James Taylor <jamestay...@apache.org> > > wrote: > &g

Re: Issues while Running Apache Phoenix against TPC-H data

On Thu, Aug 18, 2016 at 3:00 PM, James Taylor <jamestay...@apache.org> wrote: > On Thu, Aug 18, 2016 at 10:48 AM, Stack <st...@duboce.net> wrote: > ... > I'm not sure how the TCP benchmarks map to the real world use > cases of our user community. I'd think the TPC

Re: Issues while Running Apache Phoenix against TPC-H data

It was 4.7 phoenix on what version of hadoop/hbase Amit? Seven hours seems too long to load the data. > It varies greatly on a use case by use case basis and requires experimentation. Would be cool if there was a page on how to do tpc-h along with what works and what does not from the suite,

[jira] [Commented] (PHOENIX-2788) Make transactions pluggable in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205801#comment-15205801 ] stack commented on PHOENIX-2788: I didn't think you were. You were just trying help doing an an actual

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201908#comment-15201908 ] stack commented on PHOENIX-2405: bq. Add means we can have a switch to use or not use Mnemonic way

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201127#comment-15201127 ] stack commented on PHOENIX-2405: [~ywang261] bq. as Gary commented, we can use above code to allocate

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201951#comment-15201951 ] stack commented on PHOENIX-2405: bq. Thanks stack, how about fallback to Mnemonic only

hbasecon2016 cfp

The call-for-papers is open. Send in your submissions now (don't wait to the last minute -- looking at you James!). Spread the word and send in the talks. See hbasecon.com for where. Thanks all, St.Ack P.S. Also consider submitting something to berlin buzzwords. Its CfP is open till Feb 7th. It

Re: jira cleanup

Sounds good to me. St.Ack On Fri, Nov 20, 2015 at 2:55 PM, Enis Söztutar wrote: > Hi, > > It seems that we need some cleaning in the jira. I can do these changes if > it is ok with everyone. > > 1. Versions with typos are there (4.60, etc). Jira will auto-create these > release

Re: NPE between maven failsafe plugin test runs?

w to work around or get to the bottom of this NPE > we're frequently seeing (https://builds.apache.org/job/Phoenix-master/935/ > )? > I've tried locally with the -e flag, but still didn't see a stack trace... > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-fails

[jira] [Commented] (PHOENIX-1598) encode column names to save space

[ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742360#comment-14742360 ] stack commented on PHOENIX-1598: Nvm, I see the action is over in PHOENIX-1940 > encode column na

[jira] [Commented] (PHOENIX-1940) Push expected List ordinal position in KeyValueColumnExpression

[ https://issues.apache.org/jira/browse/PHOENIX-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742361#comment-14742361 ] stack commented on PHOENIX-1940: Post your patch for the peanut-gallery @larsh? > Push expected L

[jira] [Commented] (PHOENIX-1598) encode column names to save space

[ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742359#comment-14742359 ] stack commented on PHOENIX-1598: Can you point at where you would insert this Interface? Thanks

[jira] [Commented] (PHOENIX-1598) encode column names to save space

[ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733140#comment-14733140 ] stack commented on PHOENIX-1598: bq. ... would it be possible to put an interface in place in HBase

[jira] [Commented] (PHOENIX-1598) encode column names to save space

[ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732038#comment-14732038 ] stack commented on PHOENIX-1598: Thanks. > encode column names to save sp

[jira] [Commented] (PHOENIX-1598) encode column names to save space

[ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732026#comment-14732026 ] stack commented on PHOENIX-1598: Where is the mapping of short name to long name kept? Is it important

Re: Thinking of RC on Thursday

Any chance of our hurrying up this process and shipping a Phoenix that works on hbase 1.x? Thanks, St.Ack On Tue, Apr 28, 2015 at 9:42 PM, rajeshb...@apache.org chrajeshbab...@gmail.com wrote: Thanks James for confirming. Fine Ram we can include it. Thanks, Rajeshbabu. On Wed, Apr 29,

Re: Thinking of RC on Thursday

On Wed, Apr 29, 2015 at 7:09 PM, Nick Dimiduk ndimi...@gmail.com wrote: On Wed, Apr 29, 2015 at 11:08 AM, Stack st...@duboce.net wrote: Any chance of our hurrying up this process and shipping a Phoenix that works on hbase 1.x? Would be great to have a Phoenix working on HBase 1.x

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[ https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505248#comment-14505248 ] stack commented on PHOENIX-1118: bq. ...maybe we can focus on making the content

[jira] [Commented] (PHOENIX-1126) Make local index updates transactional with the data updates

[ https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485635#comment-14485635 ] stack commented on PHOENIX-1126: bq. Is there already an HBase JIRA for this? What

[jira] [Commented] (PHOENIX-1681) Use the new Region Interface

[ https://issues.apache.org/jira/browse/PHOENIX-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482575#comment-14482575 ] stack commented on PHOENIX-1681: Hang on lads. [~jonathan.lawlor] should have up

[jira] [Commented] (PHOENIX-1734) Local index improvements

[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14371563#comment-14371563 ] stack commented on PHOENIX-1734: [~rajeshbabu] Sounds good (especially bit of finding

[jira] [Commented] (PHOENIX-1734) Local index improvements

[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14367766#comment-14367766 ] stack commented on PHOENIX-1734: Approaches #1 and #2 are not viable; too many changes

Re: [DISCUSS] Phoenix supporting HBase-0.98 and HBase-1.x releases

Nice summary. Proposal looks good to me. St.Ack On Mon, Mar 16, 2015 at 3:44 PM, Enis Söztutar e...@apache.org wrote: Hi, As some of you already know, there are discussions in multiple threads in the private list, and in jira PHOENIX-1642 about what we should do to support HBase-1.0 release

Re: Joint HBase+Phoenix pow pow on or near January 15th?

Near in time to the meetup makes sense to me. Salesforce is near appdynamics and having a hard stop will force agreement (or not -- smile). St.Ack On Mon, Jan 5, 2015 at 12:13 PM, Andrew Purtell apurt...@apache.org wrote: Greetings, Next week I know at least one, probably two, HBase

[jira] [Commented] (PHOENIX-1536) Make use of SplitTransaction to split local index region from 0.98.9 onwards

[ https://issues.apache.org/jira/browse/PHOENIX-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250370#comment-14250370 ] stack commented on PHOENIX-1536: bq. I would argue the current local indexing

Re: Toward user-extensible types

If we do PInteger, etc., do we have to make DInteger for Drill types, IInteger for Impala types and TInteger for Trafodion types? St.Ack On Mon, Dec 8, 2014 at 7:01 PM, Nick Dimiduk ndimi...@gmail.com wrote: Okay, I've done as you suggested with PInteger, PFloat, c and cleaned out all the

Re: [ANNOUNCE] Samarth Jain added as Apache Phoenix committer

Congrats Samarth! St.Ack On Sat, Dec 6, 2014 at 12:10 PM, James Taylor jamestay...@apache.org wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Samarth Jain has accepted our invitation to become a committer on the Apache Phoenix project. He's been a steady contributor

[jira] [Commented] (PHOENIX-1502) Tests for Indexer won't compile after HBASE-12522

[ https://issues.apache.org/jira/browse/PHOENIX-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234558#comment-14234558 ] stack commented on PHOENIX-1502: I added you as contributor [~busbey] Tests

[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229290#comment-14229290 ] stack commented on PHOENIX-971: --- bq. ...something like the MySQL client binary protocol

[jira] [Commented] (PHOENIX-1479) IndexSplitTransaction won't compile after HBASE-12550

[ https://issues.apache.org/jira/browse/PHOENIX-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223761#comment-14223761 ] stack commented on PHOENIX-1479: +1 on what [~andrew.purt...@gmail.com] said

[jira] [Commented] (PHOENIX-1479) IndexSplitTransaction won't compile after HBASE-12550

[ https://issues.apache.org/jira/browse/PHOENIX-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223762#comment-14223762 ] stack commented on PHOENIX-1479: Can you achieve same end with a split policy

[jira] [Commented] (PHOENIX-1479) IndexSplitTransaction won't compile after HBASE-12550

[ https://issues.apache.org/jira/browse/PHOENIX-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223918#comment-14223918 ] stack commented on PHOENIX-1479: bq. but I suspect rajeshbabu took this route

[jira] [Commented] (PHOENIX-1183) phoenix-pig does not work with CDH 5.1

[ https://issues.apache.org/jira/browse/PHOENIX-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103004#comment-14103004 ] stack commented on PHOENIX-1183: PhoenixOutputFormat is compiled against wrong version

Re: [ANNOUNCE] New Apache Phoenix committer - Rajeshbabu Chintaguntla

Good on you Rajesh! On Sat, Jul 19, 2014 at 11:52 AM, Ravi Kiran maghamraviki...@gmail.com wrote: Congrats Rajesh!!! On Sat, Jul 19, 2014 at 11:29 AM, James Taylor jamestay...@apache.org wrote: On behalf of the Apache Phoenix project, I am pleased to welcome Rajeshbabu Chintaguntla as