Re: GSoC - 2016

[rajeshb...@apache.org]

Hi Pranavan,

That's good.

Have you setup hbase cluster and tried enabling tracing for queries as well[
1 <http://phoenix.apache.org/tracing.html>]? and also querying the trace
table to see the details of traces?.
Even you can try enabling tracing for specific query as for the steps
mentioned here[2
<https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14336460&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14336460>
].

Once if you are able to do that you can try loading some data with the
script PHOENIX_HOME/bin/performance.py(this create table and prepare and
load data with the number of records specified.). Then you can try running
the queries used in the performance.py script by enabling traces and check
the performance impact.

1. http://phoenix.apache.org/tracing.html
2.
https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14336460&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14336460

Please let me know if you need any help.

Thanks,
Rajeshbabu.

On Mon, Apr 4, 2016 at 1:48 PM, Pranavan Theivendiram <
pranavan...@cse.mrt.ac.lk> wrote:

> Hi Rajesh,
>
> I am able to build Apache Phoneix from the source. Shall I start and go
> ahead with fixing the JIRAS that I have mentioned in the proposal.
>
> As per James suggestion, I am going to look at JIRA -
> https://issues.apache.org/jira/browse/PHOENIX-1197 . Can you please give
> some details regarding this JIRA issue?
>
> Thanks
>
>
> *T. Pranavan*
> *BSc Eng Undergraduate| Department of Computer Science & Engineering
> ,University of Moratuwa*
> *Mobile| *0775136836
>
> On 28 March 2016 at 12:36, Pranavan Theivendiram <
> pranavan...@cse.mrt.ac.lk> wrote:
>
>> Hi Rajesh,
>>
>> I have done some initial set ups. If I find any problems, I will update
>> this mail thread with the issues.
>>
>>
>> Thanks
>> On Mar 27, 2016 11:19 PM, "rajeshb...@apache.org" <
>> chrajeshbab...@gmail.com> wrote:
>>
>>> Hi Pranavan,
>>>
>>> It's my pleasure. Glad that you are interested and you have good
>>> knowledge in that specific area.
>>> Please do some setup and testing. Happy to help you if any help needed.
>>>
>>> Thanks,
>>> Rajeshbabu.
>>>
>>>
>>> On Sun, Mar 27, 2016 at 7:40 AM, Pranavan Theivendiram <
>>> pranavan...@cse.mrt.ac.lk> wrote:
>>>
>>>> Hi Rajesh,
>>>>
>>>> Thanks for volunteering to mentor me.
>>>>
>>>>
>>>>
>>>> *T. Pranavan*
>>>> *BSc Eng Undergraduate| Department of Computer Science & Engineering
>>>> ,University of Moratuwa*
>>>> *Mobile| *0775136836
>>>>
>>>> On 27 March 2016 at 07:12, Pranavan Theivendiram <
>>>> pranavan...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Hi James,
>>>>>
>>>>> Thanks for appointing a mentor for me. I will query him for further
>>>>> clarifications.
>>>>>
>>>>> Thanks
>>>>>
>>>>> *T. Pranavan*
>>>>> *BSc Eng Undergraduate| Department of Computer Science & Engineering
>>>>> ,University of Moratuwa*
>>>>> *Mobile| *0775136836
>>>>>
>>>>> On 26 March 2016 at 22:35, James Taylor 
>>>>> wrote:
>>>>>
>>>>>> Hi Pranavan,
>>>>>>
>>>>>> Meet Rajeshbabu Chintaguntla. He's volunteered to be your mentor. All
>>>>>> docs are on our website here: https://phoenix.apache.org/tracing.html.
>>>>>> Best to ask questions on the dev list so that other community members can
>>>>>> help answer as well. Our tracing leverages Apache HTrace too, so you may
>>>>>> find more documentation on their website or through their community as 
>>>>>> well
>>>>>> (http://htrace.incubator.apache.org/). Most of the time open source
>>>>>> projects are going to be light on documentation so stepping through code 
>>>>>> in
>>>>>> Eclipse may be the best way for you to experiment.
>>>>>> See PhoenixTracingEndToEndIT along with the other classes in that 
>>>>>> package.
>>>>>>
>>>>>> Thanks,
>>>>>> James
>>>>>>
>>>>>>
>>>>>> On Friday, March 25, 2016, Pranavan Theivendiram <
>>>>&g

Re: [ANNOUNCE] New Apache Phoenix committer - Josh Elser

[rajeshb...@apache.org]

Congratulations Josh!!

On Sat, Apr 9, 2016 at 12:17 AM, Ankit Singhal 
wrote:

> Congrats Josh!!
>
> On Fri, Apr 8, 2016 at 10:29 PM, Marek Wiewiorka <
> marek.wiewio...@gmail.com>
> wrote:
>
> > Congrats!
> > 8 kwi 2016 6:57 PM "Josh Mahonin"  napisał(a):
> >
> > > Welcome aboard and congrats (fellow) Josh!
> > >
> > > On Fri, Apr 8, 2016 at 12:52 PM, James Taylor 
> > > wrote:
> > >
> > > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that
> Josh
> > > > Elser has accepted our invitation to become a committer on the Apache
> > > > Phoenix project. He's done an excellent job moving the Phoenix Query
> > > > Server[1] forward, helping us with maven issues, and being an all
> > around
> > > > good citizen by answering questions whenever they come up on the
> > mailing
> > > > lists and JIRAs.
> > > >
> > > > Welcome aboard, Josh. Looking forward to many more contributions!
> > > >
> > > > Regards,
> > > > James
> > > >
> > > > [1] https://phoenix.apache.org/server.html
> > > >
> > >
> >
>

Re: [ANNOUNCE] Ankit Singhal joins Phoenix PMC

[rajeshb...@apache.org]

Congratulations Ankit!!! Nice work.

On Wed, May 4, 2016 at 8:54 AM, Jesse Yates  wrote:

> Congrats Ankit!
>
> On Tue, May 3, 2016, 8:01 PM Nick Dimiduk  wrote:
>
> > Nice work Ankit, congrats!
> >
> > On Tuesday, May 3, 2016, James Taylor  wrote:
> >
> > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Ankit
> > > Singhal has accepted our invitation to become a member of the Apache
> > > Phoenix project management committee (PMC). Recently he's implemented
> two
> > > of the most asked for features: support for HBase namespaces [1] (a 81
> > file
> > > pull request) and support for OFFSET [2] (a 60 file pull request). Not
> > only
> > > that, but he implemented them at the SAME time!
> > >
> > > Excellent work, Ankit. Welcome aboard. Looking forward to continued
> > > collaboration.
> > >
> > > Regards,
> > > James
> > >
> > > [1] https://github.com/apache/phoenix/pull/153
> > > [2] https://github.com/apache/phoenix/pull/154
> > >
> >
>

Re: PHOENIX-2179

[rajeshb...@apache.org]

Hi Pranavan,

Have you tried limiting tracing to particular queries by trace on/off
queries. This gives the trace id of particular queries only so that you can
query tracing table matching the trace id.
You can refer[1
]
for more information.

1)
https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14336460&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14336460




On Sun, May 15, 2016 at 3:12 PM, Pranavan Theivendiram <
pranavan...@cse.mrt.ac.lk> wrote:

> Hi Devs!
>
> I am working on jira issue -
> https://issues.apache.org/jira/browse/PHOENIX-2179 . I I ran SELECT *
> FROM SYSTEM.TRACING_STATS. It took around 3 minutes and 20 seconds to
> finish. This looks cumbersome.
>
> I have come up with following alternatives.
>
>1. Limiting the trace output to the latest 1 rows.
>2. Add a parameter in query to limit the number of rows
>
> Can someone suggests which is the best one? If you have any ideas, help me
> on this issue.
>
> Thanks
>
> *T. Pranavan*
> *Junior Consultant | Department of Computer Science & Engineering
> ,University of Moratuwa*
> *Mobile| *0775136836
>

Please share the status of GSoC project

[rajeshb...@apache.org]

Hi Pranavan,

Hope you are doing well? How's the GSoC project work going on? Can you
please share the status of it and and also let's know if any help needed.
Happy to help you.

Thanks,
Rajeshbabu.

Regarding PHOENIX-1734

[rajeshb...@apache.org]

Hi Team,

As you know prior to PHOENIX-1734 we are storing all  local index data in
separate table and colocate data and index regions. To ensure proper
colocation we need customer balancer, custom split and merge logic still
these will not ensure 100% colocation. That's why we started working
PHOENIX-1734 to store local index data in separate column families in the
same table to ensure 100% colocation.

As part of PHOENIX-1734 we need to write local index udpates to same region
in preBatchMutate. When I am working with master branch(The HBase version
is 1.2.x) it went smooth and I continued the development and ensure new
implementation of local index works properly and committed the patch to
master branch as well.

But when I started porting it to other branches(HBase versions less than
1.2) I realized that write to same region is in preBatchMutate is not
allowed by HBase versions less than 1.2. There is a dependency of
HBASE-15600 to make the new local index implementation work properly for
versions less than 1.2. So I am not able to port it to other branches. I
will complete it once the next HBase point releases have HBASE-15600.

Now code in master branch is not in sync with other branches but the local
indexing feature is much more stable in master branch after PHOENIX-1734 so
I think it would be better to have PHOENIX-1734 in master branch even
porting it to other branches might delay till upcoming HBase releases
available.

Wdyt?

Thanks,
Rajeshbabu.

Re: RC on Monday

[rajeshb...@apache.org]

I can commit both PHOENIX-3002 and PHOENIX-2209 by today.

It would be better to make RC tomorrow.

Thanks,
Rajeshbabu.

On Tue, Jun 21, 2016 at 7:24 AM, James Taylor 
wrote:

> Fixes for both PHOENIX-3001 and PHOENIX-2940 have been checked in (thanks -
> nice work!). Looks like the only two outstanding are PHOENIX-3002 and
> PHOENIX-2209.
>
> Anything else missing? Can we get an RC up tomorrow (Tuesday)?
>
> Thanks,
> James
>
>
>
> On Thu, Jun 16, 2016 at 1:06 PM, Ankit Singhal  wrote:
>
> > Hi All,
> >
> > Changing the date for RC on Monday instead of Today. As following JIRAs
> > still needs to get in.
> >
> > PHOENIX-3001(NPE during split on table with deleted local Indexes.
> >
> > PHOENIX-2940(Remove Stats RPC from meta table build lock)
> >
> > Regards,
> > Ankit Singhal
> >
> > On Tue, Jun 14, 2016 at 10:51 PM, Ankit Singhal <
> ankitsingha...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > As now the Jiras which needs to go in 4.8 are either done or have +1s
> on
> > > them. so how about having RC by Thursday EOD?
> > >
> > > Checked with Rajesh too , PHOENIX-1734 is also ready for 4.x branches
> and
> > > will be committed by tomorrow.
> > >
> > > Regards,
> > > Ankit Singhal
> > >
> > >
> > > On Wed, Jun 1, 2016 at 12:33 PM, Nick Dimiduk 
> > wrote:
> > >
> > >> On Wed, Jun 1, 2016 at 10:58 AM, Josh Elser 
> > wrote:
> > >>
> > >> > I can try to help knock out some of those issues you mentioned as
> > well,
> > >> > Nick.
> > >>
> > >>
> > >> You mean my metacache woes? That's more than I'd hoped for!
> > >>
> > >> https://issues.apache.org/jira/browse/PHOENIX-2941
> > >> https://issues.apache.org/jira/browse/PHOENIX-2939
> > >> https://issues.apache.org/jira/browse/PHOENIX-2940
> > >> https://issues.apache.org/jira/browse/PHOENIX-2941
> > >>
> > >> :D
> > >>
> > >> James Taylor wrote:
> > >> >
> > >> >> Would be good to upgrade to Avatica 1.8 (PHOENIX-2960) - a vote
> > should
> > >> >> start on that today or tomorrow.
> > >> >>
> > >> >>  James
> > >> >>
> > >> >> On Tue, May 31, 2016 at 1:48 PM, Nick Dimiduk
> > >> wrote:
> > >> >>
> > >> >> We're hoping to get the shaded client jars [0] and rename of
> > >> queryserver
> > >> >>> jar [1] changes in for 4.8. There's also an optimization
> improvement
> > >> for
> > >> >>> using skip scan that's close [2].
> > >> >>>
> > >> >>> [0]: https://issues.apache.org/jira/browse/PHOENIX-2535
> > >> >>> [1]: https://issues.apache.org/jira/browse/PHOENIX-2267
> > >> >>> [2]: https://issues.apache.org/jira/browse/PHOENIX-258
> > >> >>>
> > >> >>> On Tue, May 31, 2016 at 11:07 AM, Ankit Singhal
> > >> >>> wrote:
> > >> >>>
> > >> >>> Hello Everyone,
> > >> 
> > >>  I'd like to propose a roll out of 4.8.0 RC early next week(*7th
> > >> June*)
> > >> 
> > >>  Here is the list of some good work already been done for this
> > >> release.
> > >> 
> > >>  - Local Index improvements[1]
> > >>  - Phoenix hive integration[2]
> > >>  - Namespace mapping support[3]
> > >>  - Many VIEW enhancements[4]
> > >>  - Offset support for paging queries[5]
> > >>  - 50+ Bugs resolved[6]
> > >>  - Support for HBase v1.2
> > >> 
> > >>  What else we can get in ? Is there something being actively
> worked
> > >> upon
> > >> 
> > >> >>> but
> > >> >>>
> > >>  it will not be ready by proposed date?
> > >> 
> > >> 
> > >>  Regards,
> > >>  Ankit Singhal
> > >> 
> > >> 
> > >>  [1] https://issues.apache.org/jira/browse/PHOENIX-1734
> > >>  [2] https://issues.apache.org/jira/browse/PHOENIX-2743
> > >>  [3] https://issues.apache.org/jira/browse/PHOENIX-1311
> > >>  [4] https://issues.apache.org/jira/browse/PHOENIX-1508
> > >>  [5] https://issues.apache.org/jira/browse/PHOENIX-2722
> > >>  [6] https://issues.apache.org/jira/issues/?filter=12335812
> > >> 
> > >> 
> > >> >>
> > >>
> > >
> > >
> >
>

Re: where are we at with the RC?

[rajeshb...@apache.org]

I think PHOENIX-3045 is blocker for the release. Working on it.

On Sun, Jul 3, 2016 at 10:21 AM,  wrote:

> I think I have a fix for PHOENIX-2724, that seems important to get it.
> -- Lars
>
>   From: Ankit Singhal 
>  To: James Taylor 
> Cc: "dev@phoenix.apache.org" ; Samarth Jain <
> samarth.j...@salesforce.com>; Rajeshbabu Chintaguntla <
> rchintagun...@hortonworks.com>; Thomas D'Silva ;
> Mujtaba Chohan 
>  Sent: Saturday, July 2, 2016 11:03 AM
>  Subject: Re: where are we at with the RC?
>
> Both the two Jiras(PHOENIX-2902, PHOENIX-2999) are ready with review
> comments but need to test the upgrade(and drop with cascade) on cluster.
> And , Waiting for commit of PHOENIX-2926 and fix for local index upgrade
> for multi-tenant table which is not working with latest patch on
> PHOENIX-3002.
> We will be able to do this by Monday only as I and Rajesh are in transit
> for 2 days.
> I think we can target Tuesday as RC date.
>
> Regards,
> Ankit Singhal
>
> On Fri, Jul 1, 2016 at 2:02 PM, James Taylor 
> wrote:
>
> > How we looking for the RC?
> >
> > On Friday, July 1, 2016, Samarth Jain  wrote:
> >
> >> PHOENIX-2724 has a workaround in PHOENIX-3040 that I have checked in. I
> >> think we can fix PHOENIX-2724 in a patch release, if needed.
> >>
> >> The remaining outstanding JIRAs that I know of are:
> >> https://issues.apache.org/jira/browse/PHOENIX-2902
> >> https://issues.apache.org/jira/browse/PHOENIX-29
> >> 99
> >>
> >>
> >>
> >> On Thu, Jun 30, 2016 at 9:48 PM,  wrote:
> >>
> >> > PHOENIX-3037 (Andy just committed) needs to get in.
> >> > -- Lars
> >> >  From: Samarth Jain 
> >> >  To: dev 
> >> > Cc: Ankit Singhal 
> >> >  Sent: Tuesday, June 28, 2016 9:58 AM
> >> >  Subject: Re: where are we at with the RC?
> >> >
> >> > PHOENIX-3028 is in. PHOENIX-2724 is a blocker as of now. Will work on
> >> this
> >> > today to see if it is just a matter of tuning phoenix config or
> >> something
> >> > more.
> >> > If time permits, I would like to opportunistically get PHOENIX-3035
> in.
> >> >
> >> > On Mon, Jun 27, 2016 at 10:56 PM, James Taylor <
> jamestay...@apache.org>
> >> > wrote:
> >> >
> >> > > What are the outstanding JIRAs? Would it be possible to update this
> >> daily
> >> > > so we can zero in on getting an RC up? If folks could commit there
> >> > > outstanding patches (or find a committer to do it for you), that be
> >> much
> >> > > appreciated.
> >> > >
> >> > > Thanks,
> >> > > James
> >> > >
> >> >
> >> >
> >> >
> >> >
> >>
> >
>
>
>
>

Re: where are we at with the RC?

[rajeshb...@apache.org]

I have committed the upgrade related blockers.

Thanks,
Rajeshbabu.

On Thu, Jul 7, 2016 at 10:51 PM, Mujtaba Chohan 
wrote:

> Was with Brian yesterday, PHOENIX-3056 is not a 4.8 blocker for them but
> good to have if a fix is easy.
>
> On Thu, Jul 7, 2016 at 2:54 AM,  wrote:
>
> > I assigned PHOENIX-3056 to 4.8.0, just so we won't lose track of it. If
> > it's not an issue we can move to 4.9.
> >
> >
> > --
> > *From:* James Taylor 
> > *To:* "dev@phoenix.apache.org" ; Mujtaba Chohan
> <
> > mcho...@salesforce.com>
> > *Sent:* Thursday, July 7, 2016 1:24 AM
> >
> > *Subject:* Re: where are we at with the RC?
> >
> > @Ankit, @Mujtaba - where are at now with the release? Would it be
> possible
> > to get a list of the handful of remaining JIRAs being targeted for
> > 4.8? Is PHOENIX-3056
> > a blocker?
> >
> > Thanks,
> > James
> >
> > On Tue, Jul 5, 2016 at 4:21 PM, Josh Elser  wrote:
> >
> > > Just an FYI: I re-opened PHOENIX-3025. It seems like this broke PQS
> > > somehow (PQS still expecting to find Guava in the o.a.phoenix.shaded
> > > package). Might just be something to fix at build time (hopefully,
> > anyways)
> > > -- I'm looking at it now.
> > >
> > >
> > > rajeshb...@apache.org wrote:
> > >
> > >> I think PHOENIX-3045 is blocker for the release. Working on it.
> > >>
> > >> On Sun, Jul 3, 2016 at 10:21 AM,  wrote:
> > >>
> > >> I think I have a fix for PHOENIX-2724, that seems important to get it.
> > >>> -- Lars
> > >>>
> > >>>From: Ankit Singhal
> > >>>  To: James Taylor
> > >>> Cc: "dev@phoenix.apache.org"; Samarth Jain<
> > >>> samarth.j...@salesforce.com>; Rajeshbabu Chintaguntla<
> > >>> rchintagun...@hortonworks.com>; Thomas D'Silva<
> tdsi...@salesforce.com
> > >;
> > >>> Mujtaba Chohan
> > >>>  Sent: Saturday, July 2, 2016 11:03 AM
> > >>>  Subject: Re: where are we at with the RC?
> > >>>
> > >>> Both the two Jiras(PHOENIX-2902, PHOENIX-2999) are ready with review
> > >>> comments but need to test the upgrade(and drop with cascade) on
> > cluster.
> > >>> And , Waiting for commit of PHOENIX-2926 and fix for local index
> > upgrade
> > >>> for multi-tenant table which is not working with latest patch on
> > >>> PHOENIX-3002.
> > >>> We will be able to do this by Monday only as I and Rajesh are in
> > transit
> > >>> for 2 days.
> > >>> I think we can target Tuesday as RC date.
> > >>>
> > >>> Regards,
> > >>> Ankit Singhal
> > >>>
> > >>> On Fri, Jul 1, 2016 at 2:02 PM, James Taylor
> > >>> wrote:
> > >>>
> > >>> How we looking for the RC?
> > >>>>
> > >>>> On Friday, July 1, 2016, Samarth Jain
> wrote:
> > >>>>
> > >>>> PHOENIX-2724 has a workaround in PHOENIX-3040 that I have checked
> in.
> > I
> > >>>>> think we can fix PHOENIX-2724 in a patch release, if needed.
> > >>>>>
> > >>>>> The remaining outstanding JIRAs that I know of are:
> > >>>>> https://issues.apache.org/jira/browse/PHOENIX-2902
> > >>>>> https://issues.apache.org/jira/browse/PHOENIX-29
> > >>>>> <https://issues.apache.org/jira/browse/PHOENIX-2902>99
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Thu, Jun 30, 2016 at 9:48 PM,  wrote:
> > >>>>>
> > >>>>> PHOENIX-3037 (Andy just committed) needs to get in.
> > >>>>>> -- Lars
> > >>>>>>  From: Samarth Jain
> > >>>>>>  To: dev
> > >>>>>> Cc: Ankit Singhal
> > >>>>>>  Sent: Tuesday, June 28, 2016 9:58 AM
> > >>>>>>  Subject: Re: where are we at with the RC?
> > >>>>>>
> > >>>>>> PHOENIX-3028 is in. PHOENIX-2724 is a blocker as of now. Will work
> > on
> > >>>>>>
> > >>>>> this
> > >>>>>
> > >>>>>> today to see if it is just a matter of tuning phoenix config or
> > >>>>>>
> > >>>>> something
> > >>>>>
> > >>>>>> more.
> > >>>>>> If time permits, I would like to opportunistically get
> PHOENIX-3035
> > >>>>>>
> > >>>>> in.
> > >>>
> > >>>> On Mon, Jun 27, 2016 at 10:56 PM, James Taylor<
> > >>>>>>
> > >>>>> jamestay...@apache.org>
> > >>>
> > >>>> wrote:
> > >>>>>>
> > >>>>>> What are the outstanding JIRAs? Would it be possible to update
> this
> > >>>>>>>
> > >>>>>> daily
> > >>>>>
> > >>>>>> so we can zero in on getting an RC up? If folks could commit there
> > >>>>>>> outstanding patches (or find a committer to do it for you), that
> be
> > >>>>>>>
> > >>>>>> much
> > >>>>>
> > >>>>>> appreciated.
> > >>>>>>>
> > >>>>>>> Thanks,
> > >>>>>>> James
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>
> > >>>
> > >>>
> > >>
> >
> >
> >
>

Re: Issue in Bulkload when Table name contains '-' (hyphen)

[rajeshb...@apache.org]

Hi Dharmesh,

Are you able to write to table through normal upsert query? Seems like a
bug. You can raise a JIRA for this.

Thanks,
Rajeshbabu.


On Thu, Jul 14, 2016 at 11:22 AM, Dharmesh Guna  wrote:

> Dear All,
>
> I am facing issue in bulk loading from csv files into Phoenix when my
> Phoenix table contains '-' (hyphen) in table name.
> I am using Phoenix version 4.7.0. Phoenix supports '-' (hyphen) in table
> name as per naming conventions. [a-zA-Z_0-9-.]
> If I try to bulk load using below command it fails and gives below error.
>
> sudo -u hadoop
> HADOOP_CLASSPATH=/usr/lib/hbase/hbase-protocol.jar:/usr/lib/hbase/conf/
> hadoop jar /usr/lib/phoenix/phoenix-client.jar
> org.apache.phoenix.mapreduce.CsvBulkLoadTool
> -Dfs.permissions.umask-mode=000 -t 'DMG-TEST' --input
> "/user/test/1/DMG-TEST.csv"  -d $'\t'
>
> So ultimately it removes any single or double quotes around table name
> before upserting which causes error 601.
>
> 2016-07-14 05:39:07,380 WARN [main]
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: MapTask metrics system
> already initialized!
> 2016-07-14 05:39:08,944 INFO [main]
> org.apache.phoenix.util.UpsertExecutor: Upserting SQL data with UPSERT
> INTO DMG-TEST ("APPLICATIONID", "0"."PACKAGEID") VALUES (?, ?)
> 2016-07-14 05:39:08,945 INFO [main] org.apache.hadoop.mapred.MapTask:
> Starting flush of map output
> 2016-07-14 05:39:08,952 INFO [main]
> org.apache.hadoop.io.compress.CodecPool: Got brand-new compressor [.snappy]
> 2016-07-14 05:39:08,959 WARN [main] org.apache.hadoop.mapred.YarnChild:
> Exception running child : java.lang.RuntimeException:
> org.apache.phoenix.exception.PhoenixParserException: ERROR 601 (42P00):
> Syntax error. Encountered "-" at line 1, column 17.
> at
> org.apache.phoenix.util.UpsertExecutor.createStatement(UpsertExecutor.java:83)
> at
> org.apache.phoenix.util.UpsertExecutor.(UpsertExecutor.java:94)
> at
> org.apache.phoenix.util.csv.CsvUpsertExecutor.(CsvUpsertExecutor.java:63)
> at
> org.apache.phoenix.mapreduce.CsvToKeyValueMapper.buildUpsertExecutor(CsvToKeyValueMapper.java:85)
> at
> org.apache.phoenix.mapreduce.FormatToBytesWritableMapper.setup(FormatToBytesWritableMapper.java:142)
> at
> org.apache.phoenix.mapreduce.CsvToKeyValueMapper.setup(CsvToKeyValueMapper.java:67)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:143)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:796)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:342)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.phoenix.exception.PhoenixParserException: ERROR 601
> (42P00): Syntax error. Encountered "-" at line 1, column 17.
> at
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
> at
> org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1185)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1268)
> at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.(PhoenixPreparedStatement.java:94)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.prepareStatement(PhoenixConnection.java:715)
> at
> org.apache.phoenix.util.UpsertExecutor.createStatement(UpsertExecutor.java:81)
> ... 13 more
> Caused by: NoViableAltException(94@[])
> at
> org.apache.phoenix.parse.PhoenixSQLParser.upsert_node(PhoenixSQLParser.java:4723)
> at
> org.apache.phoenix.parse.PhoenixSQLParser.oneStatement(PhoenixSQLParser.java:775)
> at
> org.apache.phoenix.parse.PhoenixSQLParser.statement(PhoenixSQLParser.java:500)
> at
> org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:108)
> ... 18 more
>
>
> Thank you!!
>
> Regards,
> :: Dharmesh Guna
> :: Development | Custom Reports
> :: Contact | 961.199.87.52 |  Ext. | 130 3264
>
>

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

[rajeshb...@apache.org]

+1
- Verified the signatures.
- Downloaded source and ran the test and all are passed.
- Downloaded tar ball and ran basic tests
- Loaded data through bulkload job and some local index tests everything
fine.
- Ran some query server related tests and everything cool.

Thanks,
Rajeshbabu.


On Fri, Jul 15, 2016 at 1:44 PM, James Taylor 
wrote:

> +1. Great work on the release, everyone! Good to have support for HBase 1.2
> now.
>
> James
>
> On Thu, Jul 14, 2016 at 6:54 AM, Ankit Singhal 
> wrote:
>
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.8.0-HBase-1.2 RC0. This is
> > the next minor release of Phoenix 4, compatible with Apache HBase 1.2.
> > The release includes both a source-only release and a convenience binary
> > release.
> >
> > This release has feature parity with our other pending 4.8.0 releases and
> > includes the following improvements:
> > - Local Index improvements[1]
> > - Phoenix hive integration[2]
> > - Namespace mapping support[3]
> > - Many VIEW enhancements[4]
> > - Offset support for paging queries[5]
> > - 100+ Bugs resolved[6]
> > - Many performance enhancements(related to StatsCache, distinct, Serial
> > query with Stats etc)
> >
> > The source tarball, including signatures, digests, etc can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.8.0-HBase-1.2-rc0/src/
> >
> > The binary artifacts can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.8.0-HBase-1.2-rc0/bin/
> >
> > For a complete list of changes, see:
> > *
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334393&projectId=12315120
> > <
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334393&projectId=12315120
> > >*
> >
> > Release artifacts are signed with the following key:
> > *https://people.apache.org/keys/committer/ankit.asc
> > *
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=c90232fbfaaf8e847703a2be3f5d147b976e2138
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=c90232fbfaaf8e847703a2be3f5d147b976e2138
> > >*
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.8.0-HBase-1.2-rc0
> >
> > Vote will be open until at least, Mon, Jul 18th @ 5pm PST. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
> > [1] https://issues.apache.org/jira/browse/PHOENIX-1734
> > [2] https://issues.apache.org/jira/browse/PHOENIX-2743
> > [3] https://issues.apache.org/jira/browse/PHOENIX-1311
> > [4] https://issues.apache.org/jira/browse/PHOENIX-1508
> > [5] https://issues.apache.org/jira/browse/PHOENIX-2722
> > [6] *https://issues.apache.org/jira/browse/filter=12337975#
> > *
> >
>

Re: Select * with empty result

[rajeshb...@apache.org]

You can use CsvBulkLoadTool provided by Phoenix than ImportTsv to load data
into the table.

https://phoenix.apache.org/bulk_dataload.html

Thanks,
Rajeshbabu.

On Wed, Jul 20, 2016 at 8:10 PM, Pandolfino Giuseppe 
wrote:

> Hi,
>
> i use Phoenix and HBASE for bulk load my dump data tables.
>
>
>
> I try to import data in a phoenix table.
>
>
>
> This is the script used to create the table:
>
> CREATE TABLE HBASE_MERC_RIC
>
> (
>
>   ID_DMERINTEGER PRIMARY KEY,
>
>   COD_SOTTOMERCATO   VARCHAR,
>
>   DSC_DIVISIONE  VARCHAR,
>
>   DSC_MERCATOVARCHAR,
>
>   DSC_SOTTO_MERCATO  VARCHAR,
>
>   ORDINTEGER
>
> );
>
>
>
> after that, i launch an importtvs operation in this way:
>
> hbase org.apache.hadoop.hbase.mapreduce.ImportTsv
> -Dimporttsv.separator=';'
> -Dimporttsv.columns="HBASE_ROW_KEY,0:cod_sottomercato,0:dsc_divisione,0:dsc_mercato,0:dsc_sotto_mercato,0:ord"
> HBASE_MERC_RIC /user/hive/warehouse/aaa/00_0
>
>
>
> where /user/hive/warehouse/aaa/00_0 is exactly the absolute path where
> my file is on HDFS.
>
>
>
> When I try to query my table using sqlline.py using a simple “SELECT *
> FROM HBASE_MERC_RIC i receive the following output:
>
>
> +--+---++--++---+
>
> | ID_DMER  | COD_SOTTOMERCATO  | DSC_DIVISIONE  | DSC_MERCATO  |
> DSC_SOTTO_MERCATO  |  ORD  |
>
>
> +--+---++--++---+
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||  |
> | null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
>  || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||  |
>   | null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null  |
>
> | null |   ||
> || null 

Re: new 4.8.0 RC?

[rajeshb...@apache.org]

Thanks Ankit,
Here is the JIRA raised PHOENIX-3111. It's not just local index issue it
can happen with upsert select, delete rows at server as well.

Thanks,
Rajeshbabu.

On Fri, Jul 22, 2016 at 5:51 PM, Ankit Singhal 
wrote:

> I was holding up the RC because Sergey and Rajesh was working on fixing the
> blocker issue they found related to LocalIndex.
> But it seems it gonna take time and will be fixed and tested by tomorrow.
> @Rajesh/Sergey, would you mind creating a JIRA and provide update on it?
>
> On Fri, Jul 22, 2016 at 12:12 PM, Ankit Singhal 
> wrote:
>
> > Yes, I'll cut the RC today. @James/Josh, how about the licensing issues
> > with tracing UI, should we include it in release or not?
> >
> > @dev, please commit the following JIRAs ASAP.
> > PHOENIX-3109
> > PHOENIX-3098
> >
> > Regards,
> > Ankit Singhal
> >
> >
> > On Fri, Jul 22, 2016 at 7:46 AM, James Taylor 
> > wrote:
> >
> >> How about a cutting a new RC now that the licensing work is complete,
> >> Ankit? Looks like we can simplify the voting too by just having a single
> >> vote across all versions by just include all the information in one VOTE
> >> thread.
> >>
> >> Would be good to get PHOENIX-3078 in too, if possible. We've had a few
> >> other fixes come in which IMHO are all ok to include in the new RC.
> >>
> >> Thanks,
> >> James
> >>
> >
> >
>

Re: Planning to cut RC by tomorrow morning IST

[rajeshb...@apache.org]

It's happening frequently in our tests which include parallel create index,
bulkload, deletes operations and automatic splits by HBase. Some times the
dead lock happen with create index and some times with deletes.

We already have a patch going under same tests. Mostly I can make final
patch in 1 or 2 days.

Thanks,
Rajeshbabu.

On Mon, Jul 25, 2016 at 9:48 PM, James Taylor 
wrote:

> Thanks, Ankit. How likely is it that PHOENIX-3111 will happen? Since it's
> not a regression and this is the first we've heard of it, maybe not very
> likely? Or is it more common with the new local index implementation? If
> it's a matter of a few days, probably worth holding off on the RC.
>
> Thoughts?
>
> On Mon, Jul 25, 2016 at 8:28 AM, Ankit Singhal 
> wrote:
>
> > Moving PHOENIX-3111 to 4.8.1 as per discussion with Rajeshbabu. Let me
> know
> > if someone thinks it's important for 4.8.0.
> > Now currently, the only outstanding blocker for 4.8.0 is PHOENIX-3113 and
> > which has a simple fix. So, by tomorrow morning IST, we should have RC1
> > out.
> >
> > Regards,
> > Ankit Singhal
> >
> >
> >
> > On Mon, Jul 25, 2016 at 10:16 AM, James Taylor 
> > wrote:
> >
> > > Can we get an RC up today, please? There's one JIRA waiting to be
> > committed
> > > and I think we're good after that. All licensing issues have been
> fixed.
> > > Thanks,
> > > James
> > >
> > > On Sunday, July 24, 2016,  wrote:
> > >
> > > > Also, can we branch 4.8-x in git?That way bigger changes can still go
> > > into
> > > > the 4.x branches, while bugs are fixed in 4.8-x branches.
> > > > -- Lars
> > > >
> > > >   From: James Taylor >
> > > >  To: "dev@phoenix.apache.org "  > > > >
> > > >  Sent: Thursday, July 21, 2016 7:16 PM
> > > >  Subject: new 4.8.0 RC?
> > > >
> > > > How about a cutting a new RC now that the licensing work is complete,
> > > > Ankit? Looks like we can simplify the voting too by just having a
> > single
> > > > vote across all versions by just include all the information in one
> > VOTE
> > > > thread.
> > > >
> > > > Would be good to get PHOENIX-3078 in too, if possible. We've had a
> few
> > > > other fixes come in which IMHO are all ok to include in the new RC.
> > > >
> > > > Thanks,
> > > > James
> > > >
> > > >
> > > >
> > >
> >
>

Re: New RC?

[rajeshb...@apache.org]

Hi James,

There is a special case in PHOENIX-3111 that if writes happen outside of
the inde building there is a chance of RTBE still. Just checking it. Will
commit the addendum in couple of hours and ping here.

Thanks,
Rajeshbabu.

On Tue, Aug 2, 2016 at 7:29 PM, James Taylor  wrote:

> Are we ready for a new RC yet?
>

Re: [VOTE] Release of Apache Phoenix 4.8.0 RC2

[rajeshb...@apache.org]

+1
- Downloaded source code and ran the IT tests all passed.
- Installed Phoenix and ran some smoke tests everything good.
- Ingested millions of rows and ran some local index related tests all logs
are fine.

Thanks,
Rajeshbabu.

On Mon, Aug 8, 2016 at 5:59 AM,  wrote:

> +1
> - Built from source- Did various tests, including perf- looks all good.
> Let's get this sucker out.
>
>   From: Ankit Singhal 
>  To: dev@phoenix.apache.org
>  Sent: Sunday, August 7, 2016 2:19 AM
>  Subject: [VOTE] Release of Apache Phoenix 4.8.0 RC2
>
> Hello Everyone,
>
> This is a call for a vote on Apache Phoenix 4.8.0 RC2. This is the next
> minor release of Phoenix 4, compatible with Apache HBase 0.98,1.0, 1.1 &
> 1.2.
> The release includes both a source-only release and a convenience
> binary release
> for each supported HBase version.
>
> The previous RC was sunk due to PHOENIX-3156 & PHOENIX-3149
>
> This release has feature parity with supported HBase versions and includes
> the following improvements:
> - Local Index improvements[1]
> - Phoenix hive integration[2]
> - Namespace mapping support[3]
> - Many VIEW enhancements[4]
> - Offset support for paging queries[5]
> - 130+ Bugs resolved
> - Many performance enhancements(related to StatsCache, distinct, Serial
> query with Stats etc)
>
> The source tarball for supported HBase versions, including signatures,
> digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.2-rc2/src/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.1-rc2/src/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.0-rc2/src/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-0.98-rc2/src/
>
> The binary artifacts for supported HBase versions can be found at:
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.2-rc2/bin/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.1-rc2/bin/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-1.0-rc2/bin/
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.8.0-HBase-0.98-rc2/bin/
>
> For a complete list of changes, see:
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12334393&projectId=12315120
>  version=12334393&projectId=12315120>*
>
> Release artifacts are signed with the following key:
> *https://people.apache.org/keys/committer/ankit.asc
> *
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/phoenix/KEYS
>
> The hashes and tags to be voted upon:
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 95926ac2bb69e5326c3aff9b41d29594a54a5cbe
>  95926ac2bb69e5326c3aff9b41d29594a54a5cbe>*
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 1b84ccbc384757d8602fcc496d94d25b78894e0a
>  1b84ccbc384757d8602fcc496d94d25b78894e0a>*
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 9e6899b2a3fe8ebbeaf95b557e103bc8f638db6c
>  9e6899b2a3fe8ebbeaf95b557e103bc8f638db6c>*
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 7c0358223c092117ce12e185f54f4061b2799b02
>  7c0358223c092117ce12e185f54f4061b2799b02>*
>
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
> tag;h=refs/tags/v4.8.0-HBase-1.2-rc2
>  tag;h=refs/tags/v4.8.0-HBase-1.2-rc2>*
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
> tag;h=refs/tags/v4.8.0-HBase-1.1-rc2
>  tag;h=refs/tags/v4.8.0-HBase-1.1-rc2>*
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
> tag;h=refs/tags/v4.8.0-HBase-1.0-rc2
>  tag;h=refs/tags/v4.8.0-HBase-1.0-rc2>*
>
> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
> tag;h=refs/tags/v4.8.0-HBase-0.98-rc2
>  tag;h=refs/tags/v4.8.0-HBase-0.98-rc2>*
> Vote will be open until at least, Wed, Aug 10th @ 2pm PST. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team
>
> [1] https://issues.apache.org/jira/browse/PHOENIX-1734
> [2] https://issues.apache.org/jira/browse/PHOENIX-2743
> [3] https://issues.apache.org/jira/browse/PHOENIX-1311
> [4] https://issues.apache.org/jira/browse/PHOENIX-1508
> [5] https://issues.apache.org/jira/browse/PHOENIX-2722
>
>
>
>

Re: [ANNOUNCE] Josh Elser joins Phoenix PMC

[rajeshb...@apache.org]

Congratulations Josh!!!

On Thu, Aug 11, 2016 at 9:17 AM, Josh Elser  wrote:

> Thank you all! I look forward to working more closely with everyone :D
>
>
> James Taylor wrote:
>
>> On behalf of the Apache Phoenix PMC, I'm pleased to announce that Josh
>> Elser has accepted our invitation to become a member of the Apache Phoenix
>> PMC. Recently he found and fixed licensing-related issues in our source
>> and
>> binary release, and prior to that he's been the force behind the Phoenix
>> Query Server (PQS).
>>
>> Really excited to have you onboard, Josh. Welcome, and looking forward to
>> continued collaboration.
>>
>> Regards,
>> James
>>
>>

Re: [ANNOUNCE] New Phoenix committer: Vincent Poon

[rajeshb...@apache.org]

Congratulations Vincent!! Great Job.

Thanks,
Rajeshbabu.

On Thu, Oct 12, 2017 at 7:21 AM, James Taylor 
wrote:

> On behalf of the Apache Phoenix PMC, I'm delighted to announce that Vincent
> Poon has accepted our invitation to become a committer. He's had a big
> impact in helping to stabilize our secondary index implementation,
> including the creation of an index scrutiny tool that will detect
> out-of-sync issues [1].
>
> Looking forward to continued contributions.
>
> Please give Vincent a warm welcome to the project!
>
> James
>
>
> [1] https://phoenix.apache.org/secondary_indexing.html#Index_Scrutiny_Tool
>

Re: [ANNOUNCE] New Phoenix committer: Ethan Wang

[rajeshb...@apache.org]

Congratulations Ethan!! Great Job.

Thanks,
Rajeshbabu.

On Thu, Oct 12, 2017 at 7:15 AM, James Taylor 
wrote:

> On behalf of the Apache Phoenix PMC, I'm please to announce that Ethan Wang
> has accepted our invitation to become a committer. He's behind some of the
> great new 4.12 features of table sampling [1] and approximate count
> distinct [2] along with contributing to the less sexy work of helping to
> stabilize our unit tests.
>
> Please give Ethan a warm welcome to the project!
>
> James
>
> [1] https://phoenix.apache.org/tablesample.html
> [2] https://phoenix.apache.org/language/functions.html#
> approx_count_distinct
>

Re: [VOTE] Apache Phoenix 5.0.0-alpha rc1

[rajeshb...@apache.org]

+1

- Tested basic, index related queries with and without stats  on large
data. All queries working fine.
- Verified cluster restart, region server restart and compaction related
cases they are ok.


Thanks,
Rajeshbabu.

On Tue, Feb 13, 2018 at 4:52 PM, Ankit Singhal 
wrote:

> +1
> - All the tests are passing(except 2 which are flaky and can be ignored).
> - Tested some basic and complex queries on cluster with large data - Ok
>
>
>
> On Tue, Feb 13, 2018 at 12:16 PM, Sergey Soldatov <
> sergeysolda...@gmail.com>
> wrote:
>
> > Tested with basic scenarios with a heavy load to salted/unsalted tables.
> > Looks stable.
> >
> > +1
> >
> > On Mon, Feb 12, 2018 at 8:01 AM, Artem Ervits 
> > wrote:
> >
> > > Hadoop 2.7.5
> > > HBase 2.0-beta1
> > > downloaded binary release: OK
> > > md5: OK
> > > loaded 1M rows with performance.py: OK
> > > ran queries in sqlline: OK
> > > started PQS and ran queries with phoenixdb python client: OK
> > > ran a java Hello World example: OK
> > >
> > >
> > > On Fri, Feb 9, 2018 at 10:34 AM, Josh Elser  wrote:
> > >
> > > > Hello Everyone,
> > > >
> > > > This is a call for a vote on Apache Phoenix 5.0.0-alpha rc1. Please
> > > notice
> > > > that there are known issues with this release which deserve the
> "alpha"
> > > > designation. These are staged on the website[1]. (Atomic upsert does
> > work
> > > > on my local installation with trivial testing)
> > > >
> > > > Over rc0, this release contains the changes: PHOENIX-4586,
> > PHOENIX-4546,
> > > > PHOENIX-4549, PHOENIX-4582.
> > > >
> > > > 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-rc1
> > > >
> > > > RC0 is based on the following commit: 451d6a37d0d461b60edff36ceb42b1
> > > > 7bb9610350
> > > >
> > > > 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/12 1600GMT). Please
> > > vote:
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > > Thanks,
> > > > The Apache Phoenix Team
> > > >
> > > > [1] https://phoenix.apache.org/release_notes.html
> > > >
> > >
> >
>

Re: [VOTE] Include python-phoenixdb into Phoenix

[rajeshb...@apache.org]

+1

On Thu, Mar 8, 2018 at 9:36 PM, Josh Elser  wrote:

> +1
>
>
> On 3/8/18 7:02 AM, Ankit Singhal wrote:
>
>> Lukas Lalinsky has graciously agreed to contribute his work on python
>> library for accessing Phoenix to Apache Phoenix project.
>>
>>
>> The details of the project can be viewed at:-
>>
>> http://python-phoenixdb.readthedocs.io/en/latest/
>>
>>
>> Code of the project:-
>>
>> https://github.com/lalinsky/python-phoenixdb
>>
>>
>> Our last discussion on the same:-
>>
>> https://www.mail-archive.com/dev@phoenix.apache.org/msg45424.html
>>
>>
>> The IP clearance steps carried out for this code can be viewed at:-
>>
>> https://issues.apache.org/jira/browse/PHOENIX-4636
>>
>>
>> Please vote to accept this code into the project:
>>
>>
>> +1 Accept the code donation
>>
>> -1 Do not accept the code donation because...
>>
>>
>> Please note that this vote is to ensure that the PMC has carried out the
>> necessary legal oversights on the incoming code and fulfilled their legal
>> obligations to the ASF so only PMC votes are binding.
>>
>>
>> However, community members are still welcome to review the code and we
>> look
>> forward to working with the community to develop this code further in the
>> future.
>>
>>
>> Thanks,
>> Ankit Singhal
>>
>>

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC3

[rajeshb...@apache.org]

+1

Downloaded the source and ran all the tests they are fine.

Thanks,
Rajeshbabu.

On Thu, Jun 7, 2018 at 9:25 PM, Thomas D'Silva 
wrote:

> +1
>
> Successfully built from source and was able run all UTs/ITs.
>
>
> On Wed, Jun 6, 2018 at 3:06 PM, Ankit Singhal 
> wrote:
>
> > +1
> >
> > * Upgrade from 4.13 to 4.14 (with HBase 1.2) - Verified
> > * Namespace mapping upgrade and mapping utility to map existing table -
> No
> > regression
> > * Query logging - verified
> >
> >
> >
> > On Wed, Jun 6, 2018 at 1:35 PM, Mujtaba Chohan 
> wrote:
> >
> > > +1.
> > >
> > > Verified backward compat. and performance looks fine when compared to
> > last
> > > release (0.98 branch).
> > >
> > > On Tue, Jun 5, 2018 at 11:50 AM, Pedro Boado 
> > > wrote:
> > >
> > > > Sure, I'll add the signature to the release repo (it's already in the
> > dev
> > > > repo) . Thanks for the reminder.
> > > >
> > > > On Tue, 5 Jun 2018, 19:36 Josh Elser,  wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > The KEYS file *must* be updated before this is released. Pedro's
> key
> > > > > does not exist at
> > > > > https://dist.apache.org/repos/dist/release/phoenix/KEYS. Pedro,
> can
> > > you
> > > > > add your key to the bottom of that file, please? There are
> > instructions
> > > > > at the top of the file.
> > > > >
> > > > > * can build all from src
> > > > > * xsums are OK, sigs are ok (given the above caveat)
> > > > > * No unexpected binaries in src release
> > > > > * mvn apache-rat:check fails in all CDH branches, but only on a
> > > > .gitignore
> > > > > * the hbase-1.1 branch is still missing the change to checksum
> > > > > generation, so it is "special" (not an issue if we just drop it
> > > anyways)
> > > > > but not wrong.
> > > > >
> > > > > On 6/5/18 10:23 AM, James Taylor wrote:
> > > > > > Hello Everyone,
> > > > > >
> > > > > > This is a call for a vote on Apache Phoenix 4.14.0 RC3. This is a
> > > patch
> > > > > > release of Phoenix 4.14 and is compatible with Apache HBase 0.98,
> > > 1.1,
> > > > > 1.2,
> > > > > > 1.3, 1.4 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes
> > > both
> > > > a
> > > > > > source-only release and a convenience binary release for each
> > > supported
> > > > > > HBase version. The prior RC was sunk due to PHOENIX-4759 which is
> > now
> > > > > fixed.
> > > > > >
> > > > > > This release has feature parity with supported HBase versions and
> > > > > includes
> > > > > > the following improvements:
> > > > > > - Over 90 bug fixes
> > > > > > - Support for HBase 1.4
> > > > > > - Support for more CDH releases
> > > > > > - Support for GRANT/REVOKE [1][2]
> > > > > > - Avoid server retries for mutable indexes [3]
> > > > > > - Pure client side transactional index maintenance [4]
> > > > > > - Prune local index regions scanned during query execution [5][6]
> > > > > > - Support NOT NULL constraint for any column for immutable table
> > [7]
> > > > > >
> > > > > > The source tarball, including signatures, digests, etc can be
> found
> > > at:
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-0.98-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.1-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.2-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.3-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.4-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.11.2-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.12.2-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.13.2-rc3/src/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.14.2-rc3/src/
> > > > > >
> > > > > > The binary artifacts can be found at:
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-0.98-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.1-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.2-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.3-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-HBase-1.4-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.11.2-rc3/bin/
> > > > > >
> > > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > > > phoenix-4.14.0-cdh5.12.2-rc3/bin/
>

Would like to make 5.0.0 RC this weekend

[rajeshb...@apache.org]

Hi Team,

We are almost ready with 4.14 release would like to make 5.0.0 rc this
weekend.

Thanks,
Rajeshbabu.

[VOTE] Release of Apache Phoenix 5.0.0 RC0

[rajeshb...@apache.org]

Hello Everyone,

This is a call for a vote on Apache Phoenix 5.0.0 RC0. This is the next
major release
of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
release
includes both a source-only release and a convenience binary release.

This release has feature parity with HBase 2.0.0 version.

Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0 recently
released.
1) Refactored coprocessor implementations as for the new coprocessor design
changes in HBase 2.0[1 
].
2) Replaced many deprecated classes/interfaces related to admin, table,
descriptor,  region,
regioninfo, connection, cell, scan and mapreduce with new ones[2
].
3) Hive and Spark integration works with latest versions of Hive(3.0.0) and
Spark respectively[3 ][4
].

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-5.0.0-HBase-2.0-rc0/src
The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-5.0.0-HBase-2.0-rc0/bin

Release artifacts are signed with the following key:
https://pgp.mit.edu/pks/lookup?op=get&search=0x318FD86BAAEDBD7B
https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v5.0.0-HBase-2.0-rc0
*https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v5.0.0-HBase-2.0-rc0
*


Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

[1] https://issues.apache.org/jira/browse/PHOENIX-4338
[2] https://issues.apache.org/jira/browse/PHOENIX-4297
[3] https://issues.apache.org/jira/browse/PHOENIX-4423
[4] https://issues.apache.org/jira/browse/PHOENIX-4527

Thanks,
The Apache Phoenix Team

[CANCEL][VOTE] Release of Apache Phoenix 5.0.0 RC0

[rajeshb...@apache.org]

Since PHOENIX-4785 <https://issues.apache.org/jira/browse/PHOENIX-4785> blocker
will spin up another RC soon.

Thanks,
Rajeshbabu.
-- Forwarded message --
From: Ankit Singhal 
Date: Thu, Jun 14, 2018 at 4:00 PM
Subject: Re: [VOTE] Release of Apache Phoenix 5.0.0 RC0
To: dev@phoenix.apache.org


https://issues.apache.org/jira/browse/PHOENIX-4785 seems to be a blocker
for the release.

On Wed, Jun 13, 2018 at 3:37 AM rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Hello Everyone,
>
> This is a call for a vote on Apache Phoenix 5.0.0 RC0. This is the next
> major release
> of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
> release
> includes both a source-only release and a convenience binary release.
>
> This release has feature parity with HBase 2.0.0 version.
>
> Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0 recently
> released.
> 1) Refactored coprocessor implementations as for the new coprocessor
design
> changes in HBase 2.0[1 <https://issues.apache.org/jira/browse/PHOENIX-4338
> >
> ].
> 2) Replaced many deprecated classes/interfaces related to admin, table,
> descriptor,  region,
> regioninfo, connection, cell, scan and mapreduce with new ones[2
> <https://issues.apache.org/jira/browse/PHOENIX-4297>].
> 3) Hive and Spark integration works with latest versions of Hive(3.0.0)
and
> Spark respectively[3 <https://issues.apache.org/jira/browse/PHOENIX-4423
> >][4
> <https://issues.apache.org/jira/browse/PHOENIX-4527>].
>
> The source tarball, including signatures, digests, etc can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
phoenix-5.0.0-HBase-2.0-rc0/src
> The binary artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-
phoenix-5.0.0-HBase-2.0-rc0/bin
>
> Release artifacts are signed with the following key:
> https://pgp.mit.edu/pks/lookup?op=get&search=0x318FD86BAAEDBD7B
> https://dist.apache.org/repos/dist/dev/phoenix/KEYS
>
> The hash and tag to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
h=refs/tags/v5.0.0-HBase-2.0-rc0
> *
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
shortlog;h=refs/tags/v5.0.0-HBase-2.0-rc0
> <
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
shortlog;h=refs/tags/v5.0.0-HBase-2.0-rc0
> >*
> <
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
h=refs/tags/v5.0.0-HBase-2.0-rc0
> >
>
> Vote will be open for at least 72 hours. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> [1] https://issues.apache.org/jira/browse/PHOENIX-4338
> [2] https://issues.apache.org/jira/browse/PHOENIX-4297
> [3] https://issues.apache.org/jira/browse/PHOENIX-4423
> [4] https://issues.apache.org/jira/browse/PHOENIX-4527
>
> Thanks,
> The Apache Phoenix Team
>

Re: [ANNOUNCE] New Phoenix PMC member: Pedro Boado

[rajeshb...@apache.org]

Congratulations, Pedro!!

On Thu, Jun 21, 2018 at 6:53 PM, Andrew Purtell 
wrote:

> Congratulations, Pedro!
>
>
> > On Jun 11, 2018, at 7:15 PM, James Taylor 
> wrote:
> >
> > On behalf of the Apache Phoenix PMC, I'm please to announce that Pedro
> > Boado has accepted our invitation to join the PMC. He's been the force
> > behind our recent support for CDH (and the reason we have support not
> only
> > for CDH 5.11 in our 4.14 release, but 5.12, 5.13, and 5.14 as well).
> >
> > Please congratulate Pedro on the excellent work he's doing.
> >
> >James
>

Re: [ANNOUNCE] New Phoenix committer: Ohad Shacham

[rajeshb...@apache.org]

Congratulations Ohad!!

On Thu, Jun 21, 2018 at 6:52 PM, Andrew Purtell 
wrote:

> Congratulations and welcome, Ohad!
>
>
> > On Jun 11, 2018, at 7:09 PM, James Taylor 
> wrote:
> >
> > On behalf of the Apache Phoenix PMC, I'm please to announce that Ohad
> > Shacham has accepted our invitation to become a committer. He's been
> > diligently working on integrating the Apache Omid transaction engine [1]
> > with Phoenix, both by enhancing Omid and by generalizing the transaction
> > interface in Phoenix [2].
> >
> > Please give Ohad a warm welcome to the team!
> >
> >James
> >
> > [1] https://omid.incubator.apache.org/
> > [2]
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=
> shortlog;h=refs/heads/omid2
>
>

Re: [ANNOUNCE] New Phoenix PMC member: Vincent Poon

[rajeshb...@apache.org]

Congratulations Vincent!!


Thanks,
Rajeshbabu.

On Thu, Jun 21, 2018 at 6:53 PM, Andrew Purtell 
wrote:

> Congratulations Vincent!
>
> Well deserved.
>
>
> > On Jun 11, 2018, at 7:20 PM, James Taylor 
> wrote:
> >
> > On behalf of the Apache Phoenix PMC, I'm please to announce that Vincent
> > Poon has accepted our invitation to join the PMC. He's been focused on
> > improving the stability and performance of secondary indexing over the
> last
> > several releases.
> >
> > Please congratulate Vincent on the fantastic job he's doing.
> >
> > Thanks,
> > James
>

[VOTE] Release of Apache Phoenix 5.0.0 RC1

[rajeshb...@apache.org]

Hello Everyone,

This is a call for a vote on Apache Phoenix 5.0.0 RC1. This is the next
major release
of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
release
includes both a source-only release and a convenience binary release. The
prior RC
was sunk due to PHOENIX-4785 which is fixed now.

This release has feature parity with HBase 2.0.0 version.

Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0 recently
released.
1) Refactored coprocessor implementations as for the new coprocessor design
changes in HBase 2.0[1 
].
2) Cleaned up deprecated APIs and leveraged new performant APIs[2
].
3) Hive and Spark integration works with latest versions of Hive(3.0.0) and
Spark respectively[3 ][4
].

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-
phoenix-5.0.0-HBase-2.0-rc1/src
The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-
phoenix-5.0.0-HBase-2.0-rc1/bin

Release artifacts are signed with the following key:
https://pgp.mit.edu/pks/lookup?op=get&search=0x318FD86BAAEDBD7B
https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
h=refs/tags/v5.0.0-HBase-2.0-rc1
*https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v5.0.0-HBase-2.0-rc1
*


Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion 
[ ] -1 disapprove (and reason why)

[1] https://issues.apache.org/jira/browse/PHOENIX-4338
[2] https://issues.apache.org/jira/browse/PHOENIX-4297
[3] https://issues.apache.org/jira/browse/PHOENIX-4423
[4] https://issues.apache.org/jira/browse/PHOENIX-4787

Thanks,
The Apache Phoenix Team

Re: [VOTE] Release of Apache Phoenix 5.0.0 RC1

[rajeshb...@apache.org]

+1

Successfully build from source and ran the tests, all are passed.

Thanks,
Rajeshbabu.


On Mon, Jul 2, 2018 at 9:45 PM, Sergey Soldatov 
wrote:

> +1
>
> Performed long run tests. No serious problems found after 12+ hours under
> moderate loaded.
>
>
>
> On Wed, Jun 27, 2018 at 9:03 PM, Josh Elser  wrote:
>
> > +1 (binding)
> >
> > Noticed that the pom.xml.versionsBackup are still present, but that's not
> > the end of the world.
> >
> >
> > On 6/26/18 1:59 PM, rajeshb...@apache.org wrote:
> >
> >> Hello Everyone,
> >>
> >> This is a call for a vote on Apache Phoenix 5.0.0 RC1. This is the next
> >> major release
> >> of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
> >> release
> >> includes both a source-only release and a convenience binary release.
> The
> >> prior RC
> >> was sunk due to PHOENIX-4785 which is fixed now.
> >>
> >> This release has feature parity with HBase 2.0.0 version.
> >>
> >> Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0 recently
> >> released.
> >> 1) Refactored coprocessor implementations as for the new coprocessor
> >> design
> >> changes in HBase 2.0[1 <https://issues.apache.org/jir
> >> a/browse/PHOENIX-4338>
> >> ].
> >> 2) Cleaned up deprecated APIs and leveraged new performant APIs[2
> >> <https://issues.apache.org/jira/browse/PHOENIX-4297>].
> >> 3) Hive and Spark integration works with latest versions of Hive(3.0.0)
> >> and
> >> Spark respectively[3 <https://issues.apache.org/
> jira/browse/PHOENIX-4423
> >> >][4
> >> <https://issues.apache.org/jira/browse/PHOENIX-4527>].
> >>
> >> The source tarball, including signatures, digests, etc can be found at:
> >> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> >> phoenix-5.0.0-HBase-2.0-rc1/src
> >> The binary artifacts can be found at:
> >> https://dist.apache.org/repos/dist/dev/phoenix/apache-
> >> phoenix-5.0.0-HBase-2.0-rc1/bin
> >>
> >> Release artifacts are signed with the following key:
> >> https://pgp.mit.edu/pks/lookup?op=get&search=0x318FD86BAAEDBD7B
> >> https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >>
> >> The hash and tag to be voted upon:
> >> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> >> h=refs/tags/v5.0.0-HBase-2.0-rc1
> >> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=sho
> >> rtlog;h=refs/tags/v5.0.0-HBase-2.0-rc1
> >> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=sho
> >> rtlog;h=refs/tags/v5.0.0-HBase-2.0-rc1>*
> >> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag
> >> ;h=refs/tags/v5.0.0-HBase-2.0-rc0>
> >>
> >> Vote will be open for at least 72 hours. Please vote:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion 
> >> [ ] -1 disapprove (and reason why)
> >>
> >> [1] https://issues.apache.org/jira/browse/PHOENIX-4338
> >> [2] https://issues.apache.org/jira/browse/PHOENIX-4297
> >> [3] https://issues.apache.org/jira/browse/PHOENIX-4423
> >> [4] https://issues.apache.org/jira/browse/PHOENIX-4787
> >>
> >> Thanks,
> >> The Apache Phoenix Team
> >>
> >>
>

Re: [VOTE] Release of Apache Phoenix 5.0.0 RC1

[rajeshb...@apache.org]

The vote is now closed and passes with 4 binding +1s and no 0 or -1 votes.
Thanks to those who voted. We'll work on pushing out the bits next.

Thanks,
Rajeshbabu.

On Tue, Jul 3, 2018 at 12:12 PM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> +1
>
> Successfully build from source and ran the tests, all are passed.
>
> Thanks,
> Rajeshbabu.
>
>
> On Mon, Jul 2, 2018 at 9:45 PM, Sergey Soldatov 
> wrote:
>
>> +1
>>
>> Performed long run tests. No serious problems found after 12+ hours under
>> moderate loaded.
>>
>>
>>
>> On Wed, Jun 27, 2018 at 9:03 PM, Josh Elser  wrote:
>>
>> > +1 (binding)
>> >
>> > Noticed that the pom.xml.versionsBackup are still present, but that's
>> not
>> > the end of the world.
>> >
>> >
>> > On 6/26/18 1:59 PM, rajeshb...@apache.org wrote:
>> >
>> >> Hello Everyone,
>> >>
>> >> This is a call for a vote on Apache Phoenix 5.0.0 RC1. This is the next
>> >> major release
>> >> of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
>> >> release
>> >> includes both a source-only release and a convenience binary release.
>> The
>> >> prior RC
>> >> was sunk due to PHOENIX-4785 which is fixed now.
>> >>
>> >> This release has feature parity with HBase 2.0.0 version.
>> >>
>> >> Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0
>> recently
>> >> released.
>> >> 1) Refactored coprocessor implementations as for the new coprocessor
>> >> design
>> >> changes in HBase 2.0[1 <https://issues.apache.org/jir
>> >> a/browse/PHOENIX-4338>
>> >> ].
>> >> 2) Cleaned up deprecated APIs and leveraged new performant APIs[2
>> >> <https://issues.apache.org/jira/browse/PHOENIX-4297>].
>> >> 3) Hive and Spark integration works with latest versions of Hive(3.0.0)
>> >> and
>> >> Spark respectively[3 <https://issues.apache.org/jir
>> a/browse/PHOENIX-4423
>> >> >][4
>> >> <https://issues.apache.org/jira/browse/PHOENIX-4527>].
>> >>
>> >> The source tarball, including signatures, digests, etc can be found at:
>> >> https://dist.apache.org/repos/dist/dev/phoenix/apache-
>> >> phoenix-5.0.0-HBase-2.0-rc1/src
>> >> The binary artifacts can be found at:
>> >> https://dist.apache.org/repos/dist/dev/phoenix/apache-
>> >> phoenix-5.0.0-HBase-2.0-rc1/bin
>> >>
>> >> Release artifacts are signed with the following key:
>> >> https://pgp.mit.edu/pks/lookup?op=get&search=0x318FD86BAAEDBD7B
>> >> https://dist.apache.org/repos/dist/dev/phoenix/KEYS
>> >>
>> >> The hash and tag to be voted upon:
>> >> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
>> >> h=refs/tags/v5.0.0-HBase-2.0-rc1
>> >> *https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=sho
>> >> rtlog;h=refs/tags/v5.0.0-HBase-2.0-rc1
>> >> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=sho
>> >> rtlog;h=refs/tags/v5.0.0-HBase-2.0-rc1>*
>> >> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag
>> >> ;h=refs/tags/v5.0.0-HBase-2.0-rc0>
>> >>
>> >> Vote will be open for at least 72 hours. Please vote:
>> >>
>> >> [ ] +1 approve
>> >> [ ] +0 no opinion 
>> >> [ ] -1 disapprove (and reason why)
>> >>
>> >> [1] https://issues.apache.org/jira/browse/PHOENIX-4338
>> >> [2] https://issues.apache.org/jira/browse/PHOENIX-4297
>> >> [3] https://issues.apache.org/jira/browse/PHOENIX-4423
>> >> [4] https://issues.apache.org/jira/browse/PHOENIX-4787
>> >>
>> >> Thanks,
>> >> The Apache Phoenix Team
>> >>
>> >>
>>
>
>

[ANNOUNCE] Apache Phoenix 5.0.0 released

[rajeshb...@apache.org]

The Apache Phoenix team is pleased to announce release of it's next major
version 5.0.0
compatible with HBase 2.0+. Apache Phoenix enables SQL-based OLTP and
operational
analytics for Apache Hadoop using Apache HBase as its backing store and
providing
integration with other projects in the Apache ecosystem such as Spark,
Hive, Pig, Flume, and
MapReduce.

The 5.0.0 release has feature parity with recently released 4.14.0.
Highlights of the release include:

* Cleanup deprecated APIs and leveraged new Performant APIs
* Refactored coprocessor implementations to make use new Coprocessor or
Observer APIs in HBase 2.0
* Hive and Spark Integration works in latest versions of Hive(3.0.0) and
Spark(2.3.0) respectively.

For more details, visit our blog here [1] and download source and binaries
here [2].

Thanks,
Rajeshbabu (on behalf of the Apache Phoenix team)

[1]
https://blogs.apache.org/phoenix/entry/apache-phoenix-releases-next-major
[2] http://phoenix.apache.org/download.html

Re: [VOTE] Release of Apache Phoenix 4.9.0 RC0

[rajeshb...@apache.org]

James,

Found PHOENIX-3433. It's a blocker. I think we need to make other RC.

Thanks,
Rajeshbabu.

On Wed, Nov 2, 2016 at 8:08 AM, 김영우 (YoungWoo Kim)  wrote:

> Hi James,
>
> I have a problem while upgrading 4.8.0 to 4.9.0 rc0. Filed PHOENIX-3432.
>
> Thanks,
> Youngwoo
>
> 2016. 11. 1. 오전 9:22에 "James Taylor" 님이 작성:
>
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.9.0 RC0. This is the next
> > minor release of Phoenix 4, compatible with Apache HBase 0.98, 1.1 & 1.2.
> > The release includes both a source-only release and a convenience binary
> > release for each supported HBase version.
> >
> > This release has feature parity with supported HBase versions and
> includes
> > the following improvements:
> > - Atomic upsert through new ON DUPLICATE KEY syntax [1]
> > - Support for DEFAULT declaration in DDL statements [2]
> > - Specify guidepost width per table [3]
> > - 38 bugs resolved
> >
> > The source tarball, including signatures, digests, etc can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-0.98-rc0/src/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-1.1-rc0/src/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-1.2-rc0/src/
> >
> > The binary artifacts can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-0.98-rc0/bin/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-1.1-rc0/bin/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.9.0-HBase-1.2-rc0/bin/
> >
> > For a complete list of changes, see:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12315120&version=12335845
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> > d45feaedbe3611cbc38e8a053f5560f391bcd2b8
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.9.0-HBase-0.98-rc0
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> > f668b010b40ff8a8f5f1d53c16bd64bd0d5a8a08
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.9.0-HBase-1.1-rc0
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> > effb095230f9f0a3e9b00e1925c6ed797ff5666c
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.9.0-HBase-1.2-rc0
> >
> > Vote will be open for 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
> >
> > [1] https://issues.apache.org/jira/browse/PHOENIX-6
> > [2] https://issues.apache.org/jira/browse/PHOENIX-476
> > [3] https://issues.apache.org/jira/browse/PHOENIX-2675
> >
>

Re: [ANNOUNCE] New Apache Phoenix committer - Kevin Liew

[rajeshb...@apache.org]

Congratulations Kevin!! Good work.

On Fri, Nov 11, 2016 at 11:08 AM, Ankit Singhal 
wrote:

> Congratulations and welcome, Kevin!!
>
> On Fri, Nov 11, 2016 at 2:10 AM, Josh Elser  wrote:
>
> > Congrats, Kevin!
> >
> >
> > James Taylor wrote:
> >
> >> On behalf of the Apache Phoenix PMC, I'm pleased to announce that Kevin
> >> Liew has accepted our invitation to become a committer on the Apache
> >> Phoenix project. He's done an great job finding and fixing many
> important
> >> Phoenix JIRAs as well as most recently implementing support for default
> >> column value declarations [1] in our upcoming 4.9.0 release.
> >>
> >> Welcome aboard, Kevin. Looking forward to many more contributions!
> >>
> >> Regards,
> >> James
> >>
> >> [1] https://issues.apache.org/jira/browse/PHOENIX-476
> >>
> >>
>

Re: Query with index failed when data table's PK column is in DESC order

[rajeshb...@apache.org]

Good catch William, Please raise JIRA and upload patch there.

http://issues.apache.org/jira/browse/PHOENIX


Thanks,
Rajeshbabu.

On Wed, Nov 16, 2016 at 1:59 PM, William  wrote:

> Hi all
>This is a very simple case, easy to repro, see the following SQLs:
>
>
>create table tt (pk integer primary key, a integer, b integer);
>create index tti on tt (a);
>upsert into tt values (1, 2, 3);
>select /*+index(tt tti)*/ b from tt where a = 2; // will query
> back to data table
>//this SELECT works fine, will return b=3
>
>create table tt2 (pk integer primary key desc, a integer, b integer);
>create index tt2i on tt2 (a);
>upsert into tt2 values (1, 2, 3);
>select /*+index(tt2 tt2i)*/ b from tt2 where a = 2;
>// this SELECT should return the same result set, but actually returned
> an empty ResultSet
>
>The only difference between tt2 and tt is that pk column of tt2 is in
> DESC order. But the same SELECT returns nothing for tt2. The reason of this
> bug is in HashCacheClient#evaluateKeyExpression(). In line 173,
> type.toObject() didn't take sort order as a param. All we have to do is to
> pass child.getSortOrder() to type.toObject() method.
>
>
>Just modify this line like this:
>   values.add(LiteralExpression.newConstant(type.toObject(ptr,
> child.getSortOrder()), type));
>
>
>I checked the code in trunk and this bug still exists. Are there any
> similar scenarios that failed considering the sort order information?
>
>
> Thanks.
> William

Re: Dropping local index on large table caused crash of region servers

[rajeshb...@apache.org]

Dropping local index index issues scan and in the coprocessors we prepare
index data and write back to same table.  To avoid the timeout you can
increase scanner timeout/rpc timeout and phoenix client timeout values as
well.

If you have many guideposts then we might issue many parallel scans to the
same RS which might have added lot of overhead.
Try dropping the index with less number of guideposts on the table.

Actually during major compaction we can automatically skip writing back the
deleted index details so we can just drop meta data. I am checking this
improvement. Raised https://issues.apache.org/jira/browse/PHOENIX-3566 for
the same.

Thanks,
Rajeshbabu.

On Thu, Jan 5, 2017 at 7:16 PM, 김영우 (YoungWoo Kim)  wrote:

> Hi,
>
> I've faced crash of RS when I'm dropping local index from very large table.
> I have several tables with billions of row and the tables are hosted on
> HBase 1.2.4 and Phoenix 4.9.0
>
> Each region server reported 'gc pause' from their logs and it's strange to
> me because, the log messages are popped up when I drop local indexes.
> eventually, my query failed with timeout. any other operations like
> insert/bulkload data or querying data works fine.
>
> I'm not sure but dropping local indexes from large table is expensive. Is
> there any workaround for this?
>
> Thanks,
> Youngwoo
>

Thinking of RC on Thursday

[rajeshb...@apache.org]

I'd like to propose we can have 4.4.0 RC on Thursday.
We have got a lot of great stuff in 4.4.0 already:
- 60 bug fixed(which includes fixes from 4.3.1)
- Spart integration
- Query server
- Union All support
- Pherf - load tester measures throughput
- Many math and date/time buit-in functions
- MR job to populate indexes
- Support for 1.0.x (create new 4.4.0 branch for this)

- PHOENIX-538 Support UDFs JIRA is very close.

Is there any others that we should try to get in?

Thanks,
Rajeshbabu.

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

That's good to have Eli. I have marked 4.4.0 as fix version for the JIRA.

Thanks,
Rajeshbabu.

On Tue, Apr 21, 2015 at 2:27 AM, Eli Levine  wrote:

> Rajesh, I'm harboring hopes of getting PHOENIX-900 completed by Thursday.
> Hopefully it'll end up in 4.4. I'll keep you posted.
>
> Thanks
>
> Eli
>
> On Mon, Apr 20, 2015 at 1:42 PM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > I'd like to propose we can have 4.4.0 RC on Thursday.
> > We have got a lot of great stuff in 4.4.0 already:
> > - 60 bug fixed(which includes fixes from 4.3.1)
> > - Spart integration
> > - Query server
> > - Union All support
> > - Pherf - load tester measures throughput
> > - Many math and date/time buit-in functions
> > - MR job to populate indexes
> > - Support for 1.0.x (create new 4.4.0 branch for this)
> >
> > - PHOENIX-538 Support UDFs JIRA is very close.
> >
> > Is there any others that we should try to get in?
> >
> > Thanks,
> > Rajeshbabu.
> >
>

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

That's really great work James. Thanks for pointing.

On Tue, Apr 21, 2015 at 11:47 AM, James Taylor 
wrote:

> Good list, Rajeshbabu. Thanks for starting the RC process. One more of
> note that's already in:
>
> - 7.5x performance improvement for non aggregate, unordered queries
> (PHOENIX-1779).
>
> Thanks,
> James
>
> On Mon, Apr 20, 2015 at 2:02 PM, rajeshb...@apache.org
>  wrote:
> > That's good to have Eli. I have marked 4.4.0 as fix version for the JIRA.
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Tue, Apr 21, 2015 at 2:27 AM, Eli Levine  wrote:
> >
> >> Rajesh, I'm harboring hopes of getting PHOENIX-900 completed by
> Thursday.
> >> Hopefully it'll end up in 4.4. I'll keep you posted.
> >>
> >> Thanks
> >>
> >> Eli
> >>
> >> On Mon, Apr 20, 2015 at 1:42 PM, rajeshb...@apache.org <
> >> chrajeshbab...@gmail.com> wrote:
> >>
> >> > I'd like to propose we can have 4.4.0 RC on Thursday.
> >> > We have got a lot of great stuff in 4.4.0 already:
> >> > - 60 bug fixed(which includes fixes from 4.3.1)
> >> > - Spart integration
> >> > - Query server
> >> > - Union All support
> >> > - Pherf - load tester measures throughput
> >> > - Many math and date/time buit-in functions
> >> > - MR job to populate indexes
> >> > - Support for 1.0.x (create new 4.4.0 branch for this)
> >> >
> >> > - PHOENIX-538 Support UDFs JIRA is very close.
> >> >
> >> > Is there any others that we should try to get in?
> >> >
> >> > Thanks,
> >> > Rajeshbabu.
> >> >
> >>
>

It's time to create branch for 1.0.x and/or 1.1.x

[rajeshb...@apache.org]

Hi Team,

I think this is better time to create 4.4 branch to work with 1.0.x.

Also HBase 1.1 also very close to release we can have 4.4 branch to work
with it.
I expect very minimal/no changes required for it.
So that we can release 4.4 with all three major versions of HBase.


What do you think?


Thanks,
Rajeshbabu.

Re: It's time to create branch for 1.0.x and/or 1.1.x

[rajeshb...@apache.org]

James, I think Andrew already landed patches for that. May need minor
changes.
I can create branch for 1.1 and  push the patches after rebase.
What do you say?

Thanks,
Rajeshbabu.

On Tue, Apr 21, 2015 at 10:43 PM, James Taylor 
wrote:

> For a Phoenix release on HBase 1.1, I think it's important to complete
> the work to be on supported HBase APIs (PHOENIX-1681, PHOENIX-1717).
>
> Thanks,
> James
>
> On Tue, Apr 21, 2015 at 1:31 AM, rajeshb...@apache.org
>  wrote:
> > Hi Team,
> >
> > I think this is better time to create 4.4 branch to work with 1.0.x.
> >
> > Also HBase 1.1 also very close to release we can have 4.4 branch to work
> > with it.
> > I expect very minimal/no changes required for it.
> > So that we can release 4.4 with all three major versions of HBase.
> >
> >
> > What do you think?
> >
> >
> > Thanks,
> > Rajeshbabu.
>

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

Thanks all for pointing and working on the JIRA.
Some of them already committed. Thanks Eli, Samarth Jain,Cody Marcel for
quick turn around.

@Samarth
https://issues.apache.org/jira/browse/PHOENIX-1819
When we can expect the patch for this?

If we are not able to complete the list by tomorrow then I can take RC
around next Tuesday.
By the mean time I will create branches for 1.0.x and 1.1(If it's ok) as
well and see the health of it(do some testing).
What do you say?

I think no progress for PHOENIX-1673. Any one want to take it?
@Sergey Belousov are you interested in it?

Thanks,
Rajeshbabu.


On Wed, Apr 22, 2015 at 9:38 PM, Sergey Belousov 
wrote:

> would be  nice if
> https://issues.apache.org/jira/browse/PHOENIX-1673
> makes to 4.4
>  On Apr 22, 2015 11:42 AM, "Cody Marcel"  wrote:
>
> > I have sort of combined PHOENIX-1728
> > <https://issues.apache.org/jira/browse/PHOENIX-1728> and PHOENIX-1729
> > <https://issues.apache.org/jira/browse/PHOENIX-1729>. I hopefully will
> > have
> > a pull request today for those. PHOENIX-1727
> > <https://issues.apache.org/jira/browse/PHOENIX-1727> will likely be a
> bit
> > before I can work on. Work internally, particularly support for mixed r/w
> > workloads (not sure if there is a Jira yet) seems to be higher priority.
> >
> > On Tue, Apr 21, 2015 at 4:32 PM, James Taylor 
> > wrote:
> >
> > > Another couple that need to go into 4.4.0 release IMO are PHOENIX-1728
> > > (Pherf - Make tests use mini cluster so that unit test run at build
> > > time) and PHOENIX-1727 (Pherf - Port shell scripts to python).
> > > Thanks,
> > > James
> > >
> > > On Tue, Apr 21, 2015 at 11:19 AM, James Taylor  >
> > > wrote:
> > > > You're welcome (and Samarth did the work). Thanks,
> > > >
> > > > James
> > > >
> > > > On Tue, Apr 21, 2015 at 1:19 AM, rajeshb...@apache.org
> > > >  wrote:
> > > >> That's really great work James. Thanks for pointing.
> > > >>
> > > >> On Tue, Apr 21, 2015 at 11:47 AM, James Taylor <
> > jamestay...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Good list, Rajeshbabu. Thanks for starting the RC process. One more
> > of
> > > >>> note that's already in:
> > > >>>
> > > >>> - 7.5x performance improvement for non aggregate, unordered queries
> > > >>> (PHOENIX-1779).
> > > >>>
> > > >>> Thanks,
> > > >>> James
> > > >>>
> > > >>> On Mon, Apr 20, 2015 at 2:02 PM, rajeshb...@apache.org
> > > >>>  wrote:
> > > >>> > That's good to have Eli. I have marked 4.4.0 as fix version for
> the
> > > JIRA.
> > > >>> >
> > > >>> > Thanks,
> > > >>> > Rajeshbabu.
> > > >>> >
> > > >>> > On Tue, Apr 21, 2015 at 2:27 AM, Eli Levine  >
> > > wrote:
> > > >>> >
> > > >>> >> Rajesh, I'm harboring hopes of getting PHOENIX-900 completed by
> > > >>> Thursday.
> > > >>> >> Hopefully it'll end up in 4.4. I'll keep you posted.
> > > >>> >>
> > > >>> >> Thanks
> > > >>> >>
> > > >>> >> Eli
> > > >>> >>
> > > >>> >> On Mon, Apr 20, 2015 at 1:42 PM, rajeshb...@apache.org <
> > > >>> >> chrajeshbab...@gmail.com> wrote:
> > > >>> >>
> > > >>> >> > I'd like to propose we can have 4.4.0 RC on Thursday.
> > > >>> >> > We have got a lot of great stuff in 4.4.0 already:
> > > >>> >> > - 60 bug fixed(which includes fixes from 4.3.1)
> > > >>> >> > - Spart integration
> > > >>> >> > - Query server
> > > >>> >> > - Union All support
> > > >>> >> > - Pherf - load tester measures throughput
> > > >>> >> > - Many math and date/time buit-in functions
> > > >>> >> > - MR job to populate indexes
> > > >>> >> > - Support for 1.0.x (create new 4.4.0 branch for this)
> > > >>> >> >
> > > >>> >> > - PHOENIX-538 Support UDFs JIRA is very close.
> > > >>> >> >
> > > >>> >> > Is there any others that we should try to get in?
> > > >>> >> >
> > > >>> >> > Thanks,
> > > >>> >> > Rajeshbabu.
> > > >>> >> >
> > > >>> >>
> > > >>>
> > >
> >
>

org.apache.phoenix.end2end.index.DropIndexDuringUpsertIT frequently failing

[rajeshb...@apache.org]

The test case failing because some Hudson problem. Anyone has idea how
to solve this?


Failed to read test report file
/home/jenkins/jenkins-slave/workspace/Phoenix-master/phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.DropIndexDuringUpsertIT.xml
org.dom4j.DocumentException: Error on line 62 of document
file:///home/jenkins/jenkins-slave/workspace/Phoenix-master/phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.DropIndexDuringUpsertIT.xml
: XML document structures must start and end within the same entity.
Nested exception: XML document structures must start and end within
the same entity.
at org.dom4j.io.SAXReader.read(SAXReader.java:482)
at org.dom4j.io.SAXReader.read(SAXReader.java:264)
at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123)
at hudson.tasks.junit.TestResult.parse(TestResult.java:273)
at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:229)
at hudson.tasks.junit.TestResult.parse(TestResult.java:164)
at hudson.tasks.junit.TestResult.parse(TestResult.java:147)
at hudson.tasks.junit.TestResult.(TestResult.java:123)
at 
hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117)
at 
hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXParseException; systemId:
file:///home/jenkins/jenkins-slave/workspace/Phoenix-master/phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.DropIndexDuringUpsertIT.xml;
lineNumber: 62; columnNumber: 26; XML document structures must start
and end within the same entity.
at 
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at 
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at 
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
at 
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
at 
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:903)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:563)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1384)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1774)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(XMLEntityScanner.java:1252)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(XMLDocumentFragmentScannerImpl.java:1653)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3004)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
at org.dom4j.io.SAXReader.read(SAXReader.java:465)
... 18 more
Nested exception:
org.xml.sax.SAXParseException; systemId:
file:///home/jenkins/jenkins-slave/workspace/Phoenix-master/phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.DropIndexDuringUpsertIT.xml;
lineNumber: 62; columnNumber:

Re: Phoenix branch integrations

[rajeshb...@apache.org]

4.x-HBase-1.0 branch has deleted by Enis/James.

I have created branches 4.4-HBase-1.0 and 4.4-HBase-1.1 from master. You
should be able to commit the branches.

On Sat, Apr 25, 2015 at 12:33 AM, Cody Marcel 
wrote:

> I am a little confused about the where to commit changes. Yesterday I
> committed to Master
> <
> https://github.com/apache/phoenix/commit/254024f9c97ffa541fbc097a89e2bd2859fa02a2
> >.
> I now that change when I look at branches 4.4-HBase-1.0 and 4.4-HBase-1.1.
> I did not have to commit there. I don't see it in 4.x-HBase-1.0.
>
> There seems to be some auto integration going on for some, but not all
> branches.
>

Re: The BuildBot is live!

[rajeshb...@apache.org]

Great work Nick.
Just one thing now it's running only unit tests it seems. What about
integration tests? It would be better to make the scripts run integration
tests as well.


Thanks,
Rajeshbabu.

On Fri, Apr 24, 2015 at 9:18 AM, Nick Dimiduk  wrote:

> On Thu, Apr 23, 2015 at 7:19 PM, James Taylor 
> wrote:
>
> > Excellent, Nick. For us non HBasers, what's the recommended workflow?
> >
>
> Generate a patch from your sandbox. Committers will be committing a local
> patch before pushing upstream, so you'll have the commit there. You can
> generate a patch with `git diff` or `git format-patch` as you like. Attach
> the patch to the JIRA. If the patch is for a specific branch, i.e., 4.3,
> include "4.3" in the file name. Press the "Submit Patch" button (I think
> this is only available if the JIRA is assigned to you). Now you wait. The
> upstream job looks for new "patch available" tickets every 5 minutes. It
> will kick off our buildbot. After it's done it's thing, it will post it's
> analysis on your ticket.
>
> Only check-in if our BuildBot passes?
> >
>
> Generally yes. I was going to suggest we adopt this policy once we're
> comfortable the scripts are working and the builds are reliable. In the
> common case, we should only be pushing patches that have received a
> favorable review from the build bot. We need to decide what "favorable"
> means to Phoenix. It's a tool to keep us honest -- it's no replacement for
> a human reviewer's +1.
>
> On Thu, Apr 23, 2015 at 4:37 PM, Enis Söztutar  wrote:
> > > Great work! You the man.
> > >
> > > Enis
> > >
> > > On Thu, Apr 23, 2015 at 4:35 PM, Mujtaba Chohan 
> > wrote:
> > >
> > >> That's awesome Nick!
> > >>
> > >> On Thu, Apr 23, 2015 at 4:30 PM, Eli Levine 
> > wrote:
> > >>
> > >> > Great work, Nick! Thanks for doing this.
> > >> >
> > >> > Eli
> > >> >
> > >> > On Thu, Apr 23, 2015 at 4:01 PM, Nick Dimiduk 
> > >> wrote:
> > >> >
> > >> > > Devs --
> > >> > >
> > >> > > We now have a pre-commit BuildBot [0]! Our pedantic build-checking
> > >> robot
> > >> > > servant passed its first judgement [1] this afternoon. It is a
> clone
> > >> [2]
> > >> > of
> > >> > > the buildbot from HBase, so it's somber tone should be familiar to
> > many
> > >> > of
> > >> > > you. Same rules apply -- attach your patch, hit "Submit Patch" and
> > the
> > >> > > tools will pick up from there.
> > >> > >
> > >> > > Our robot is about as intelligent as a young dog, it's pretty
> > flexible
> > >> in
> > >> > > applying whatever kind of patch file you give it. It's also able
> to
> > >> look
> > >> > at
> > >> > > the patch file name and decide which branch it should be run
> > against.
> > >> So
> > >> > > far it's been trained to work with branches "3.0," "3.2," "4.0.1,"
> > >> "4.2,"
> > >> > > "4.3 4.x-HBase-0.98," and "master". Include any of those
> explicitly
> > in
> > >> > your
> > >> > > patch name and it'll run on vs that branch. Master is the default.
> > You
> > >> > can
> > >> > > train it for new branches by adding them to the properties file
> [3].
> > >> > >
> > >> > > Let me know if you have any issues, or just open tickets and fix
> 'em
> > >> > > yourselves ;)
> > >> > > -n
> > >> > >
> > >> > > [0]: https://builds.apache.org/job/PreCommit-PHOENIX-Build/
> > >> > > [1]:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> https://issues.apache.org/jira/browse/PHOENIX-1909?focusedCommentId=14509986&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14509986
> > >> > > [2]:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=blob;f=dev/test-patch.sh;h=1ed7e6224093aebae78f18869ff069153e0437ea;hb=HEAD
> > >> > > [3]:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=blob;f=dev/test-patch.properties;h=6a82eeefa540687b73a54d36275067b61f4c8775;hb=HEAD#l30
> > >> > >
> > >> >
> > >>
> >
>

Re: The BuildBot is live!

[rajeshb...@apache.org]

Thanks Nick. I will change it.


Thanks.
Rajeshbabu.

On Sun, Apr 26, 2015 at 11:57 PM, Nick Dimiduk  wrote:

> Sure Rajesh, I have no problem with that, so long as Apache doesn't raise
> alarm. This is simple enough to do by editing the runTests method [0]. You
> want to give it a go? Let me know if you have any troubles.
>
> [0]: https://github.com/apache/phoenix/blob/master/dev/test-patch.sh#L833
>
> On Sat, Apr 25, 2015 at 12:53 AM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > Great work Nick.
> > Just one thing now it's running only unit tests it seems. What about
> > integration tests? It would be better to make the scripts run integration
> > tests as well.
> >
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Fri, Apr 24, 2015 at 9:18 AM, Nick Dimiduk 
> wrote:
> >
> > > On Thu, Apr 23, 2015 at 7:19 PM, James Taylor 
> > > wrote:
> > >
> > > > Excellent, Nick. For us non HBasers, what's the recommended workflow?
> > > >
> > >
> > > Generate a patch from your sandbox. Committers will be committing a
> local
> > > patch before pushing upstream, so you'll have the commit there. You can
> > > generate a patch with `git diff` or `git format-patch` as you like.
> > Attach
> > > the patch to the JIRA. If the patch is for a specific branch, i.e.,
> 4.3,
> > > include "4.3" in the file name. Press the "Submit Patch" button (I
> think
> > > this is only available if the JIRA is assigned to you). Now you wait.
> The
> > > upstream job looks for new "patch available" tickets every 5 minutes.
> It
> > > will kick off our buildbot. After it's done it's thing, it will post
> it's
> > > analysis on your ticket.
> > >
> > > Only check-in if our BuildBot passes?
> > > >
> > >
> > > Generally yes. I was going to suggest we adopt this policy once we're
> > > comfortable the scripts are working and the builds are reliable. In the
> > > common case, we should only be pushing patches that have received a
> > > favorable review from the build bot. We need to decide what "favorable"
> > > means to Phoenix. It's a tool to keep us honest -- it's no replacement
> > for
> > > a human reviewer's +1.
> > >
> > > On Thu, Apr 23, 2015 at 4:37 PM, Enis Söztutar 
> wrote:
> > > > > Great work! You the man.
> > > > >
> > > > > Enis
> > > > >
> > > > > On Thu, Apr 23, 2015 at 4:35 PM, Mujtaba Chohan <
> mujt...@apache.org>
> > > > wrote:
> > > > >
> > > > >> That's awesome Nick!
> > > > >>
> > > > >> On Thu, Apr 23, 2015 at 4:30 PM, Eli Levine 
> > > > wrote:
> > > > >>
> > > > >> > Great work, Nick! Thanks for doing this.
> > > > >> >
> > > > >> > Eli
> > > > >> >
> > > > >> > On Thu, Apr 23, 2015 at 4:01 PM, Nick Dimiduk <
> > ndimi...@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > > Devs --
> > > > >> > >
> > > > >> > > We now have a pre-commit BuildBot [0]! Our pedantic
> > build-checking
> > > > >> robot
> > > > >> > > servant passed its first judgement [1] this afternoon. It is a
> > > clone
> > > > >> [2]
> > > > >> > of
> > > > >> > > the buildbot from HBase, so it's somber tone should be
> familiar
> > to
> > > > many
> > > > >> > of
> > > > >> > > you. Same rules apply -- attach your patch, hit "Submit Patch"
> > and
> > > > the
> > > > >> > > tools will pick up from there.
> > > > >> > >
> > > > >> > > Our robot is about as intelligent as a young dog, it's pretty
> > > > flexible
> > > > >> in
> > > > >> > > applying whatever kind of patch file you give it. It's also
> able
> > > to
> > > > >> look
> > > > >> > at
> > > > >> > > the patch file name and decide which branch it should be run
> > > > against.
> > > > >> So
> > > > >> > > far it's been trained to work with branches "3.0," "3.2,"
> > "4.0.1,"
> > > > >> "4.2,"
> > > > >> > > "4.3 4.x-HBase-0.98," and "master". Include any of those
> > > explicitly
> > > > in
> > > > >> > your
> > > > >> > > patch name and it'll run on vs that branch. Master is the
> > default.
> > > > You
> > > > >> > can
> > > > >> > > train it for new branches by adding them to the properties
> file
> > > [3].
> > > > >> > >
> > > > >> > > Let me know if you have any issues, or just open tickets and
> fix
> > > 'em
> > > > >> > > yourselves ;)
> > > > >> > > -n
> > > > >> > >
> > > > >> > > [0]: https://builds.apache.org/job/PreCommit-PHOENIX-Build/
> > > > >> > > [1]:
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/PHOENIX-1909?focusedCommentId=14509986&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14509986
> > > > >> > > [2]:
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=blob;f=dev/test-patch.sh;h=1ed7e6224093aebae78f18869ff069153e0437ea;hb=HEAD
> > > > >> > > [3]:
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=blob;f=dev/test-patch.properties;h=6a82eeefa540687b73a54d36275067b61f4c8775;hb=HEAD#l30
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
>

Re: [DISCUSS] branch names

[rajeshb...@apache.org]

>
>- delete the 4.4-HBase-1.1 branch and do this work in master.
>- rename the 4.4-HBase-1.0 branch to 4.x-HBase-1.0.
>- create the 4.4-HBase-1.0 branch off of 4.x-HBase-1.0 a bit later
>
I agree with this Enis and but I too feel create 4.4-HBase-1.0 before RC is
better than before RC vote is going to pass.

Thanks,
Rajeshbabu.

On Tue, Apr 28, 2015 at 12:30 AM, Enis Söztutar  wrote:

> >
> >
> > My proposal would be:
> > - delete the 4.4-HBase-1.1 branch and do this work in master.
> >
>
> Sounds good. We will not have 4.4 release for HBase-1.1.0 until HBase
> release is done. Rajesh what do you think?
>
> - rename the 4.4-HBase-1.0 branch to 4.x-HBase-1.0.
> >
>
> +1.
>
>
> > - create the 4.4-HBase-1.0 branch off of 4.x-HBase-1.0 a bit later
> > (when it looks like an RC is going to pass) and warn folks not to
> > commit JIRAs not approved by the RM while the voting is going on.
> >
>
> I think the RC has to be cut from the branch after forking. That is the
> cleanest approach IMO. Creating the fork, just before cutting the RC is
> equal amounts of work.
>
>
> >
> > Thanks,
> > James
> >
> > On Mon, Apr 27, 2015 at 11:30 AM, Enis Söztutar  wrote:
> > > I think, it depends on whether we want master to have 5.0.0-SNAPSHOT
> > > version or 4.5.0-SNAPSHOT version and whether we want 4.5 and further
> > > releases for HBase-1.0.x series. Personally, I would love to see at
> least
> > > one release of Phoenix for 1.0.x, but it is fine if Phoenix decides to
> > only
> > > do 4.4 for HBase-1.0 and 4.5 for 1.1.
> > >
> > > If we want to have a place for 5.0.0-SNAPSHOT, you are right that we
> > should
> > > do 4.x-HBase-1.0 branch, and fork 4.4-HBase-1.0 branch from there. I
> > guess,
> > > Rajesh's creating of 4.4 branch is for preparing for the 4.4 soon.
> > >
> > > Enis
> > >
> > > On Mon, Apr 27, 2015 at 10:16 AM, James Taylor  >
> > > wrote:
> > >
> > >> I think the 4.4-HBase-1.0 and 4.4-HBase-1.1 are misnamed and we're
> > >> making the same mistake we did before by calling our branch 4.0. Once
> > >> the 4.4 release goes out and we're working on 4.5, we're going to have
> > >> to check 4.5 work into the 4.4-HBase-1.0 and 4.4-HBase-1.1 branches
> > >> (which is confusing).
> > >>
> > >> Instead, we should name the branches 4.x-HBase-1.0 and 4.x-HBase-1.1.
> > >> When we're ready to release, we can create a 4.4 branch from each of
> > >> these branches and the 4.x-HBase-1.0 and 4.x-HBase-1.1 will continue
> > >> to be used for 4.5. If we plan on patch releases to 4.4, they'd be
> > >> made out of the 4.4 branch.
> > >>
> > >> Thoughts?
> > >>
> >
>

Re: [DISCUSS] branch names

[rajeshb...@apache.org]

Hi Team,

Here is the plan for branch names(Just reiterating what ever James
suggested):

1) As HBase 1.1.0 release may take 1 or 2 weeks currently we can delete
4.4-HBase-1.1 branch as James mentioned. We can target it for 4.4.1 release.
Today I will delete the branch if no objections.

2) rename the 4.4-HBase-1.0 branch to 4.x-HBase-1.0.
Create 4.x-HBase-1.0 branch from 4.4-HBase-1.0 and delete 4.4-HBase-1.0.
Will do it today.

3) RC can be created from 4.x-HBase-1.0 and 4.4-HBase-1.0 can be created
just
before RC going to pass to avoid overhead of committing to two branches.

Is that ok?

Thanks,
Rajeshbabu.

On Tue, Apr 28, 2015 at 11:37 PM, Nick Dimiduk  wrote:

> FYI, HBase 1.1.0 is imminent. I will push another snapshot jar today that's
> very close, and hope to have rc0 up Wednesday (tomorrow).
>
> On Mon, Apr 27, 2015 at 12:20 PM, James Taylor 
> wrote:
>
> > Do you agree we need to create a 4.x-HBase-1.0 branch now? If not,
> > what branch will be used to check-in work for 4.5? The reason *not* to
> > create the 4.4-HBase-1.0 branch now is that every check-in needs to be
> > merged with *both* a 4.x-HBase-1.0 branch and the 4.4-HBase-1.0
> > branch. This is wasted effort until the branches diverge (which I
> > suspect they won't until after the 4.4 release).
> >
> > Thanks,
> > James
> >
> > On Mon, Apr 27, 2015 at 12:13 PM, rajeshb...@apache.org
> >  wrote:
> > >>
> > >>- delete the 4.4-HBase-1.1 branch and do this work in master.
> > >>- rename the 4.4-HBase-1.0 branch to 4.x-HBase-1.0.
> > >>- create the 4.4-HBase-1.0 branch off of 4.x-HBase-1.0 a bit later
> > >>
> > > I agree with this Enis and but I too feel create 4.4-HBase-1.0 before
> RC
> > is
> > > better than before RC vote is going to pass.
> > >
> > > Thanks,
> > > Rajeshbabu.
> > >
> > > On Tue, Apr 28, 2015 at 12:30 AM, Enis Söztutar 
> > wrote:
> > >
> > >> >
> > >> >
> > >> > My proposal would be:
> > >> > - delete the 4.4-HBase-1.1 branch and do this work in master.
> > >> >
> > >>
> > >> Sounds good. We will not have 4.4 release for HBase-1.1.0 until HBase
> > >> release is done. Rajesh what do you think?
> > >>
> > >> - rename the 4.4-HBase-1.0 branch to 4.x-HBase-1.0.
> > >> >
> > >>
> > >> +1.
> > >>
> > >>
> > >> > - create the 4.4-HBase-1.0 branch off of 4.x-HBase-1.0 a bit later
> > >> > (when it looks like an RC is going to pass) and warn folks not to
> > >> > commit JIRAs not approved by the RM while the voting is going on.
> > >> >
> > >>
> > >> I think the RC has to be cut from the branch after forking. That is
> the
> > >> cleanest approach IMO. Creating the fork, just before cutting the RC
> is
> > >> equal amounts of work.
> > >>
> > >>
> > >> >
> > >> > Thanks,
> > >> > James
> > >> >
> > >> > On Mon, Apr 27, 2015 at 11:30 AM, Enis Söztutar 
> > wrote:
> > >> > > I think, it depends on whether we want master to have
> 5.0.0-SNAPSHOT
> > >> > > version or 4.5.0-SNAPSHOT version and whether we want 4.5 and
> > further
> > >> > > releases for HBase-1.0.x series. Personally, I would love to see
> at
> > >> least
> > >> > > one release of Phoenix for 1.0.x, but it is fine if Phoenix
> decides
> > to
> > >> > only
> > >> > > do 4.4 for HBase-1.0 and 4.5 for 1.1.
> > >> > >
> > >> > > If we want to have a place for 5.0.0-SNAPSHOT, you are right that
> we
> > >> > should
> > >> > > do 4.x-HBase-1.0 branch, and fork 4.4-HBase-1.0 branch from
> there. I
> > >> > guess,
> > >> > > Rajesh's creating of 4.4 branch is for preparing for the 4.4 soon.
> > >> > >
> > >> > > Enis
> > >> > >
> > >> > > On Mon, Apr 27, 2015 at 10:16 AM, James Taylor <
> > jamestay...@apache.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > >> I think the 4.4-HBase-1.0 and 4.4-HBase-1.1 are misnamed and
> we're
> > >> > >> making the same mistake we did before by calling our branch 4.0.
> > Once
> > >> > >> the 4.4 release goes out and we're working on 4.5, we're going to
> > have
> > >> > >> to check 4.5 work into the 4.4-HBase-1.0 and 4.4-HBase-1.1
> branches
> > >> > >> (which is confusing).
> > >> > >>
> > >> > >> Instead, we should name the branches 4.x-HBase-1.0 and
> > 4.x-HBase-1.1.
> > >> > >> When we're ready to release, we can create a 4.4 branch from each
> > of
> > >> > >> these branches and the 4.x-HBase-1.0 and 4.x-HBase-1.1 will
> > continue
> > >> > >> to be used for 4.5. If we plan on patch releases to 4.4, they'd
> be
> > >> > >> made out of the 4.4 branch.
> > >> > >>
> > >> > >> Thoughts?
> > >> > >>
> > >> >
> > >>
> >
>

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

Devs,

Thanks folks for picking up the JIRAs and fixing most of them in the list
quickly.

PHOENIX-628 & PHOENIX-1710 are in progress. James any idea how much time
they will take to commit?
I can wait for one more day to complete the work.

Still no work started at below JIRAs and since they are improvements I
think we can move them to next version.
- PHOENIX-1673
- PHOENIX-1727
- PHOENIX-1819

Thanks,
Rajeshbabu.

On Sat, Apr 25, 2015 at 12:57 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Hi Devs,
>
> I have created branches  4.4-HBase-1.0 and 4.4-HBase-1.1  from master to
> work with 1.0.x and 1.1.x respectively.
> If any changes further should be committed to the branches as well. Please
> don't miss.
>
> Thanks,
> Rajeshbabu.
>
> On Thu, Apr 23, 2015 at 4:35 AM, Sergey Belousov <
> sergey.belou...@gmail.com> wrote:
>
>> I am interested in it (kind of show stopper for us) but I am totally
>> swamp.
>> at work at home... just one of thouse periods.
>>
>> hopefully will have some brake next month or earlier.
>>
>> sorry
>> On Apr 22, 2015 4:38 PM, "rajeshb...@apache.org" <
>> chrajeshbab...@gmail.com>
>> wrote:
>>
>> > Thanks all for pointing and working on the JIRA.
>> > Some of them already committed. Thanks Eli, Samarth Jain,Cody Marcel for
>> > quick turn around.
>> >
>> > @Samarth
>> > https://issues.apache.org/jira/browse/PHOENIX-1819
>> > When we can expect the patch for this?
>> >
>> > If we are not able to complete the list by tomorrow then I can take RC
>> > around next Tuesday.
>> > By the mean time I will create branches for 1.0.x and 1.1(If it's ok) as
>> > well and see the health of it(do some testing).
>> > What do you say?
>> >
>> > I think no progress for PHOENIX-1673. Any one want to take it?
>> > @Sergey Belousov are you interested in it?
>> >
>> > Thanks,
>> > Rajeshbabu.
>> >
>> >
>> > On Wed, Apr 22, 2015 at 9:38 PM, Sergey Belousov <
>> > sergey.belou...@gmail.com>
>> > wrote:
>> >
>> > > would be  nice if
>> > > https://issues.apache.org/jira/browse/PHOENIX-1673
>> > > makes to 4.4
>> > >  On Apr 22, 2015 11:42 AM, "Cody Marcel" 
>> wrote:
>> > >
>> > > > I have sort of combined PHOENIX-1728
>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1728> and
>> PHOENIX-1729
>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1729>. I hopefully
>> will
>> > > > have
>> > > > a pull request today for those. PHOENIX-1727
>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1727> will likely
>> be a
>> > > bit
>> > > > before I can work on. Work internally, particularly support for
>> mixed
>> > r/w
>> > > > workloads (not sure if there is a Jira yet) seems to be higher
>> > priority.
>> > > >
>> > > > On Tue, Apr 21, 2015 at 4:32 PM, James Taylor <
>> jamestay...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Another couple that need to go into 4.4.0 release IMO are
>> > PHOENIX-1728
>> > > > > (Pherf - Make tests use mini cluster so that unit test run at
>> build
>> > > > > time) and PHOENIX-1727 (Pherf - Port shell scripts to python).
>> > > > > Thanks,
>> > > > > James
>> > > > >
>> > > > > On Tue, Apr 21, 2015 at 11:19 AM, James Taylor <
>> > jamestay...@apache.org
>> > > >
>> > > > > wrote:
>> > > > > > You're welcome (and Samarth did the work). Thanks,
>> > > > > >
>> > > > > > James
>> > > > > >
>> > > > > > On Tue, Apr 21, 2015 at 1:19 AM, rajeshb...@apache.org
>> > > > > >  wrote:
>> > > > > >> That's really great work James. Thanks for pointing.
>> > > > > >>
>> > > > > >> On Tue, Apr 21, 2015 at 11:47 AM, James Taylor <
>> > > > jamestay...@apache.org>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >>> Good list, Rajeshbabu. Thanks for starting the RC process. One
>> > more
>> > > > of
>> > > > > >>> note tha

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

Thanks James for confirming. Fine Ram we can include it.

Thanks,
Rajeshbabu.

On Wed, Apr 29, 2015 at 10:07 AM, Vasudevan, Ramkrishna S <
ramkrishna.s.vasude...@intel.com> wrote:

> By chance saw this mail.  If we are ok with PHOENIX-1856 we can take that
> also.
>
> -Original Message-
> From: James Taylor [mailto:jamestay...@apache.org]
> Sent: Wednesday, April 29, 2015 8:28 AM
> To: dev@phoenix.apache.org
> Subject: Re: Thinking of RC on Thursday
>
> Thanks, Rajeshbabu. I think all of those JIRAs can be pushed to the next
> release. The only one that's a must fix is PHOENIX-1930. Thomas is looking
> at it now and should be able to give you a time estimate tomorrow for it.
> Thanks,
> James
>
> On Tue, Apr 28, 2015 at 7:37 PM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
> > Devs,
> >
> > Thanks folks for picking up the JIRAs and fixing most of them in the
> > list quickly.
> >
> > PHOENIX-628 & PHOENIX-1710 are in progress. James any idea how much
> > time they will take to commit?
> > I can wait for one more day to complete the work.
> >
> > Still no work started at below JIRAs and since they are improvements I
> > think we can move them to next version.
> > - PHOENIX-1673
> > - PHOENIX-1727
> > - PHOENIX-1819
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Sat, Apr 25, 2015 at 12:57 AM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> Hi Devs,
> >>
> >> I have created branches  4.4-HBase-1.0 and 4.4-HBase-1.1  from master
> >> to work with 1.0.x and 1.1.x respectively.
> >> If any changes further should be committed to the branches as well.
> >> Please don't miss.
> >>
> >> Thanks,
> >> Rajeshbabu.
> >>
> >> On Thu, Apr 23, 2015 at 4:35 AM, Sergey Belousov <
> >> sergey.belou...@gmail.com> wrote:
> >>
> >>> I am interested in it (kind of show stopper for us) but I am totally
> >>> swamp.
> >>> at work at home... just one of thouse periods.
> >>>
> >>> hopefully will have some brake next month or earlier.
> >>>
> >>> sorry
> >>> On Apr 22, 2015 4:38 PM, "rajeshb...@apache.org" <
> >>> chrajeshbab...@gmail.com>
> >>> wrote:
> >>>
> >>> > Thanks all for pointing and working on the JIRA.
> >>> > Some of them already committed. Thanks Eli, Samarth Jain,Cody
> >>> > Marcel for quick turn around.
> >>> >
> >>> > @Samarth
> >>> > https://issues.apache.org/jira/browse/PHOENIX-1819
> >>> > When we can expect the patch for this?
> >>> >
> >>> > If we are not able to complete the list by tomorrow then I can
> >>> > take RC around next Tuesday.
> >>> > By the mean time I will create branches for 1.0.x and 1.1(If it's
> >>> > ok) as well and see the health of it(do some testing).
> >>> > What do you say?
> >>> >
> >>> > I think no progress for PHOENIX-1673. Any one want to take it?
> >>> > @Sergey Belousov are you interested in it?
> >>> >
> >>> > Thanks,
> >>> > Rajeshbabu.
> >>> >
> >>> >
> >>> > On Wed, Apr 22, 2015 at 9:38 PM, Sergey Belousov <
> >>> > sergey.belou...@gmail.com>
> >>> > wrote:
> >>> >
> >>> > > would be  nice if
> >>> > > https://issues.apache.org/jira/browse/PHOENIX-1673
> >>> > > makes to 4.4
> >>> > >  On Apr 22, 2015 11:42 AM, "Cody Marcel"
> >>> > > 
> >>> wrote:
> >>> > >
> >>> > > > I have sort of combined PHOENIX-1728
> >>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1728> and
> >>> PHOENIX-1729
> >>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1729>. I
> >>> > > > hopefully
> >>> will
> >>> > > > have
> >>> > > > a pull request today for those. PHOENIX-1727
> >>> > > > <https://issues.apache.org/jira/browse/PHOENIX-1727> will
> >>> > > > likely
> >>> be a
> >>> > > bit
> >>> > > > before I can work on. Work internally, particularly support
> >>> > > > for
>

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

I wil make RC once  PHOENIX-1773 verified.

Thanks,
Rajeshbabu.
On Thu, Apr 30, 2015 at 12:25 PM, James Taylor 
wrote:

> PHOENIX-1930 was resolved, but PHOENIX-1773 may be another b/w compat
> issue. Need to sync with Mujtaba to figure out how to repro.
>
> On Wed, Apr 29, 2015 at 7:20 PM, Stack  wrote:
> > On Wed, Apr 29, 2015 at 7:09 PM, Nick Dimiduk 
> wrote:
> >
> >> On Wed, Apr 29, 2015 at 11:08 AM, Stack  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 for HBaseCon :)
> >>
> >>
> > That would be nice.
> >
> > My main concern is that over in YARN-3411 they are considering of doing
> > hbase 0.98 APIs because there is no phoenix for hbase-1.0.0 yet.
> >
> > St.Ack
>

Re: Thinking of RC on Thursday

[rajeshb...@apache.org]

Mujtaba confirmed that PHOENIX-1773 is not a problem.
The tests are very stable now. I ran multiple times and not even single
failure.
So I am going to create a RC today.

Thanks,
Rajeshbabu.

On Thu, Apr 30, 2015 at 7:11 PM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> I wil make RC once  PHOENIX-1773 verified.
>
> Thanks,
> Rajeshbabu.
>
> On Thu, Apr 30, 2015 at 12:25 PM, James Taylor 
> wrote:
>
>> PHOENIX-1930 was resolved, but PHOENIX-1773 may be another b/w compat
>> issue. Need to sync with Mujtaba to figure out how to repro.
>>
>> On Wed, Apr 29, 2015 at 7:20 PM, Stack  wrote:
>> > On Wed, Apr 29, 2015 at 7:09 PM, Nick Dimiduk 
>> wrote:
>> >
>> >> On Wed, Apr 29, 2015 at 11:08 AM, Stack  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 for HBaseCon :)
>> >>
>> >>
>> > That would be nice.
>> >
>> > My main concern is that over in YARN-3411 they are considering of doing
>> > hbase 0.98 APIs because there is no phoenix for hbase-1.0.0 yet.
>> >
>> > St.Ack
>>
>
>

No commits to 4.x-HBase-0.98 & 4.x-HBase-1.0

[rajeshb...@apache.org]

Please hold on commits to 4.x-HBase-0.98 & 4.x-HBase-1.0 while I prepare
for RC.

Re: No commits to 4.x-HBase-0.98 & 4.x-HBase-1.0

[rajeshb...@apache.org]

RC is tagged and posted. You may resume in 4.x-HBase-0.98 & 4.x-HBase-1.0 -
only bug fixes please.

Thanks,
Rajeshbabu.

On Fri, May 1, 2015 at 4:55 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Please hold on commits to 4.x-HBase-0.98 & 4.x-HBase-1.0 while I prepare
> for RC.
>

Fwd: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0

[rajeshb...@apache.org]

-- Forwarded message --
From: rajeshb...@apache.org 
Date: Sat, May 2, 2015 at 7:45 AM
Subject: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0
To: "dev@phoenix.apache.org" 


This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC0. This is the
next minor release of Phoenix 4, compatible with the 1.0(branch of
Apache HBase(1.0.1+) . The release includes both a source-only release and a
convenience binary release.

The 4.4.0-HBase-1.0 release has feature parity with our pending
4.4.0-HBase-0.98 release.  New features include:
- Support HBase HA Query(timeline-consistent region replica read)[1]
- Alter session query support(at present changing query consistency level.
Can be used for changing connection properties.)

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/src/
<https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/>

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/bin/
<https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/>

Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=81298547ba034e29589bb4c79b0bddbe97a8939e
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc0

<https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
For a complete list of changes, see:
<https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
<https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin

<https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[1] https://issues.apache.org/jira/browse/PHOENIX-1683

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC0

[rajeshb...@apache.org]

On Sat, May 2, 2015 at 7:27 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC0. This is
> the
> next minor release of Phoenix 4, compatible with the 0.98 branch of
> Apache HBase. The release includes both a source-only release and a
> convenience binary release.
>
> Highlights of the release include:
> - spark integration[1]
> - query server[2]
> - 7.5x performance improvement for non aggregate, unordered queries[3]
> - pherf - load tester measures throughput[4]
> - support union All and union queries in subquery
>(PHOENIX-1580,PHOENIX-1807).
> - support for user defined functions(PHOENIX-538)
> - many math and date/time buit-in functions
>(PHOENIX-1662, PHOENIX-1660)
> - mr job to populate indexes(PHOENIX-1609)
> - improvements in tracing and monitoring.
> - some more improvements in CBO
> - over 70 bug fixes and etc...
>
> For a complete list of changes, see:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
>
> The source tarball, including signatures, digests, etc can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/
>
> The binary artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/
>
> Release artifacts are signed with the following key:
> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/phoenix/KEYS
>
> The hash and tag to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc0
>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> Vote will be open for at least 72 hours. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team
>
> [1] https://issues.apache.org/jira/secure/attachment/12723640/README.md
> [2] http://phoenix.apache.org/server.html
> <http://phoenix.apache.org/server.html>
> [3] https://issues.apache.org/jira/browse/PHOENIX-1779
> [4] http://phoenix.apache.org/pherf.html
>
>

[VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0

[rajeshb...@apache.org]

This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC0. This is the
next minor release of Phoenix 4, compatible with the 1.0(branch of
Apache HBase(1.0.1+) . The release includes both a source-only release and a
convenience binary release.

The 4.4.0-HBase-1.0 release has feature parity with our pending
4.4.0-HBase-0.98 release.  New features include:
- Support HBase HA Query(timeline-consistent region replica read)[1]
- Alter session query support(at present changing query consistency level.
Can be used for changing connection properties.)

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/src/


The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/bin/


Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=81298547ba034e29589bb4c79b0bddbe97a8939e
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc0


For a complete list of changes, see:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin


Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[1] https://issues.apache.org/jira/browse/PHOENIX-1683

[VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC0

[rajeshb...@apache.org]

This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC0. This is
the
next minor release of Phoenix 4, compatible with the 0.98 branch of
Apache HBase. The release includes both a source-only release and a
convenience binary release.

Highlights of the release include:
- spark integration[1]
- query server[2]
- 7.5x performance improvement for non aggregate, unordered queries[3]
- pherf - load tester measures throughput[4]
- support union All and union queries in subquery
   (PHOENIX-1580,PHOENIX-1807).
- support for user defined functions(PHOENIX-538)
- many math and date/time buit-in functions
   (PHOENIX-1662, PHOENIX-1660)
- mr job to populate indexes(PHOENIX-1609)
- improvements in tracing and monitoring.
- some more improvements in CBO
- over 70 bug fixes and etc...

For a complete list of changes, see:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/

Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc0


Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[1] https://issues.apache.org/jira/secure/attachment/12723640/README.md
[2] http://phoenix.apache.org/server.html

[3] https://issues.apache.org/jira/browse/PHOENIX-1779
[4] http://phoenix.apache.org/pherf.html

Re: 4.4.0 RCs?

[rajeshb...@apache.org]

It's fine James. I am pushing the RCs.

Thanks,
Rajeshbabu.

On Sat, May 2, 2015 at 5:22 AM, James Taylor  wrote:

> Hi Rajeshbabu,
> Anything we can do to help get the RCs out?
> Thanks,
> James
>

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC0

[rajeshb...@apache.org]

Hi Team,
Gentle reminder for voting. Already 3 days over.

Thanks,
Rajeshbabu.

On Tue, May 5, 2015 at 7:51 AM, James Taylor  wrote:

> We typically push to maven after the release, but it'd be nice to
> stage it before as it makes it easier to test.
> Thanks,
> James
>
> On Mon, May 4, 2015 at 7:04 PM, Enis Söztutar  wrote:
> > Are we not doing maven artifacts as a part of the release? I can see the
> > previous artifacts in the maven repo, but not "staged" in the maven
> staging
> > repo. Are we pushing it to maven after the RC vote passed?
> >
> > In HBase, at the time of the release candidate, we push the artifacts
> > (using maven deploy) so that we can make sure that the artifacts at the
> > maven repo is created from the same bits.
> >
> > See https://hbase.apache.org/book.html#releasing.
> >
> > Enis
> >
> > On Sat, May 2, 2015 at 9:11 AM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> On Sat, May 2, 2015 at 7:27 AM, rajeshb...@apache.org <
> >> chrajeshbab...@gmail.com> wrote:
> >>
> >> > This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC0.
> This is
> >> > the
> >> > next minor release of Phoenix 4, compatible with the 0.98 branch of
> >> > Apache HBase. The release includes both a source-only release and a
> >> > convenience binary release.
> >> >
> >> > Highlights of the release include:
> >> > - spark integration[1]
> >> > - query server[2]
> >> > - 7.5x performance improvement for non aggregate, unordered queries[3]
> >> > - pherf - load tester measures throughput[4]
> >> > - support union All and union queries in subquery
> >> >(PHOENIX-1580,PHOENIX-1807).
> >> > - support for user defined functions(PHOENIX-538)
> >> > - many math and date/time buit-in functions
> >> >(PHOENIX-1662, PHOENIX-1660)
> >> > - mr job to populate indexes(PHOENIX-1609)
> >> > - improvements in tracing and monitoring.
> >> > - some more improvements in CBO
> >> > - over 70 bug fixes and etc...
> >> >
> >> > For a complete list of changes, see:
> >> >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
> >> >
> >> > The source tarball, including signatures, digests, etc can be found
> at:
> >> >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/
> >> >
> >> > The binary artifacts can be found at:
> >> >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/
> >> >
> >> > Release artifacts are signed with the following key:
> >> > http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> >> >
> >> > KEYS file available here:
> >> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >> >
> >> > The hash and tag to be voted upon:
> >> >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> >> >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc0
> >> >
> >> >
> >> > <
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> >> >
> >> > Vote will be open for at least 72 hours. Please vote:
> >> >
> >> > [ ] +1 approve
> >> > [ ] +0 no opinion
> >> > [ ] -1 disapprove (and reason why)
> >> >
> >> > Thanks,
> >> > The Apache Phoenix Team
> >> >
> >> > [1]
> https://issues.apache.org/jira/secure/attachment/12723640/README.md
> >> > [2] http://phoenix.apache.org/server.html
> >> > <http://phoenix.apache.org/server.html>
> >> > [3] https://issues.apache.org/jira/browse/PHOENIX-1779
> >> > [4] http://phoenix.apache.org/pherf.html
> >> >
> >> >
> >>
>

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0

[rajeshb...@apache.org]

Hi Team,
Gentle reminder for voting. Already 3 days over.

Thanks,
Rajeshbabu.

On Sat, May 2, 2015 at 7:45 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC0. This is
> the
> next minor release of Phoenix 4, compatible with the 1.0(branch of
> Apache HBase(1.0.1+) . The release includes both a source-only release and
> a
> convenience binary release.
>
> The 4.4.0-HBase-1.0 release has feature parity with our pending
> 4.4.0-HBase-0.98 release.  New features include:
> - Support HBase HA Query(timeline-consistent region replica read)[1]
> - Alter session query support(at present changing query consistency level.
> Can be used for changing connection properties.)
>
> The source tarball, including signatures, digests, etc can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/src/
> <https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/>
>
> The binary artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/bin/
> <https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/>
>
> Release artifacts are signed with the following key:
> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/phoenix/KEYS
>
> The hash and tag to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=81298547ba034e29589bb4c79b0bddbe97a8939e
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc0
>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> For a complete list of changes, see:
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> Vote will be open for at least 72 hours. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team
>
> [1] https://issues.apache.org/jira/browse/PHOENIX-1683
>
>

Re: Issue with running sqlline (phoenix 4.4 RC0)

[rajeshb...@apache.org]

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  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  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  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 
>> 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 <
>> >> sergey.belou...@gmail.com>
>> >> 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"  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 <
>> >> > sergey.belou...@gmail.com
>> >> > > >
>> >> > > 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" 
>> 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 <
>> >> > > > > sergey.belou...@gmail.com>
>> >> > > > > 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 
>> >> > > > > > 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/../
>> >> > > > > > li

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0

[rajeshb...@apache.org]

bin scripts are not working as expected with make_rc.sh layout
(PHOENIX-1948) & NPE while inserting null in a VARCHAR array in upsert
stmt(PHOENIX-1949) turns into critical. I will sink this RC and make other
on Friday.

Thanks,
Rajeshbabu.

On Wed, May 6, 2015 at 4:24 AM, Ravi Kiran 
wrote:

> +1 from me.
>
> On Tue, May 5, 2015 at 8:36 AM, Samarth Jain 
> wrote:
>
> > +1
> >
> > On Fri, May 1, 2015 at 7:15 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> > > This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC0. This
> is
> > > the
> > > next minor release of Phoenix 4, compatible with the 1.0(branch of
> > > Apache HBase(1.0.1+) . The release includes both a source-only release
> > and
> > > a
> > > convenience binary release.
> > >
> > > The 4.4.0-HBase-1.0 release has feature parity with our pending
> > > 4.4.0-HBase-0.98 release.  New features include:
> > > - Support HBase HA Query(timeline-consistent region replica read)[1]
> > > - Alter session query support(at present changing query consistency
> > level.
> > > Can be used for changing connection properties.)
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/src/
> > > <
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/
> > > >
> > >
> > > The binary artifacts can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc0/bin/
> > > <
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/
> > > >
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=81298547ba034e29589bb4c79b0bddbe97a8939e
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc0
> > >
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > > >
> > > For a complete list of changes, see:
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > > >
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
> > >
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > > >
> > > Vote will be open for at least 72 hours. Please vote:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > The Apache Phoenix Team
> > >
> > > [1] https://issues.apache.org/jira/browse/PHOENIX-1683
> > >
> >
>

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC0

[rajeshb...@apache.org]

bin scripts are not working as expected with make_rc.sh layout
(PHOENIX-1948) & NPE while inserting null in a VARCHAR array in upsert
stmt(PHOENIX-1949) turns into critical. I will sink this RC and make other
on Friday.

Thanks,
Rajeshbabu.

On Wed, May 6, 2015 at 4:24 AM, Ravi Kiran 
wrote:

> +1
>
> Have done the necessary validations of spark feature also.
>
>
>
> On Tue, May 5, 2015 at 8:36 AM, Samarth Jain 
> wrote:
>
> > +1
> >
> > On Fri, May 1, 2015 at 6:57 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> > > This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC0. This
> is
> > > the
> > > next minor release of Phoenix 4, compatible with the 0.98 branch of
> > > Apache HBase. The release includes both a source-only release and a
> > > convenience binary release.
> > >
> > > Highlights of the release include:
> > > - spark integration[1]
> > > - query server[2]
> > > - 7.5x performance improvement for non aggregate, unordered queries[3]
> > > - pherf - load tester measures throughput[4]
> > > - support union All and union queries in subquery
> > >(PHOENIX-1580,PHOENIX-1807).
> > > - support for user defined functions(PHOENIX-538)
> > > - many math and date/time buit-in functions
> > >(PHOENIX-1662, PHOENIX-1660)
> > > - mr job to populate indexes(PHOENIX-1609)
> > > - improvements in tracing and monitoring.
> > > - some more improvements in CBO
> > > - over 70 bug fixes and etc...
> > >
> > > For a complete list of changes, see:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/src/
> > >
> > > The binary artifacts can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98-rc0/bin/
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc0
> > >
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> > > >
> > > Vote will be open for at least 72 hours. Please vote:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > The Apache Phoenix Team
> > >
> > > [1]
> https://issues.apache.org/jira/secure/attachment/12723640/README.md
> > > [2] http://phoenix.apache.org/server.html
> > > <http://phoenix.apache.org/server.html>
> > > [3] https://issues.apache.org/jira/browse/PHOENIX-1779
> > > [4] http://phoenix.apache.org/pherf.html
> > >
> >
>

Re: Issue with running sqlline (phoenix 4.4 RC0)

[rajeshb...@apache.org]

Hi Sergey,

I thought it was automated in release script. But next time when I cut RC
will take care of it.
Thanks for checking.

Thanks,
Rajeshbabu.

On Thu, May 7, 2015 at 8:27 AM, Sergey Belousov 
wrote:

> 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.(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 <
> sergey.belou...@gmail.com> wrote:
>
>> thank you Nick
>> will  check first thing in the morning
>> On May 5, 2015 10:56 PM, "Nick Dimiduk"  wrote:
>>
>>> Please have a look at https://issues.apache.org/jira/browse/PHOENIX-1948
>>>
>>> On Tue, May 5, 2015 at 6:19 PM, rajeshb...@apache.org <
>>> chrajeshbab...@gmail.com> 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 
>>> 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 
>>> 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
>>> >&

Going to make RC for 4.4-HBase-0.98, 4.4-HBase-1.0

[rajeshb...@apache.org]

[CANCEL][VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC0

[rajeshb...@apache.org]

Found couple of issues that sunk this RC:
https://issues.apache.org/jira/browse/PHOENIX-1948
https://issues.apache.org/jira/browse/PHOENIX-1949

Fix for the two issue are checked in. Will roll out a new RC soon.

[CANCEL][VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC0

[rajeshb...@apache.org]

Found couple of issues that sunk this RC:
https://issues.apache.org/jira/browse/PHOENIX-1948
https://issues.apache.org/jira/browse/PHOENIX-1949

Fix for the two issue are checked in. Will roll out a new RC soon.

[VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC1

[rajeshb...@apache.org]

Hi Everyone,

This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC1. This is
the
next minor release of Phoenix 4, compatible with the 0.98 branch of
Apache HBase. The release includes both a source-only release and a
convenience binary release.

Highlights of the release include:
- spark integration[1]
- query server[2]
- 7.5x performance improvement for non aggregate, unordered queries[3]
- pherf - load tester measures throughput[4]
- support union All and union queries in subquery
   (PHOENIX-1580,PHOENIX-1807).
- support for user defined functions(PHOENIX-538)
- many math and date/time buit-in functions
   (PHOENIX-1662, PHOENIX-1660)
- mr job to populate indexes(PHOENIX-1609)
- improvements in tracing and monitoring.
- some more improvements in CBO
- over 70 bug fixes and etc...

For a complete list of changes, see:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/src/


The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/bin/


Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=4126cb3f7e5fcd69ba03e2fb24778ec47051c39b
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc1

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[1] http://phoenix.apache.org/phoenix_spark.html
[2] http://phoenix.apache.org/server.html

[3] https://issues.apache.org/jira/browse/PHOENIX-1779
[4] http://phoenix.apache.org/pherf.html

[VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC1

[rajeshb...@apache.org]

Hi Everyone,

This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC1. This is the
next minor release of Phoenix 4, compatible with the 1.0(branch of
Apache HBase(1.0.1+) . The release includes both a source-only release and a
convenience binary release.

The 4.4.0-HBase-1.0 release has feature parity with our pending
4.4.0-HBase-0.98 release.  New features include:
- Support HBase HA Query(timeline-consistent region replica read)[1]
- Alter session query support(at present changing query consistency level.
Can be used for changing connection properties.)

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc1/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc1/bin/

Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=09d1840876d7b55e32d753b541eb7df22b85
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc1

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[1] https://issues.apache.org/jira/browse/PHOENIX-1683

Re: Going to make RC for 4.4-HBase-0.98, 4.4-HBase-1.0

[rajeshb...@apache.org]

Hi Sergey,
I have sent new RCs for voting. Please have a look at them.

Thanks,
Rajeshbabu.

On Mon, May 11, 2015 at 8:29 PM, Sergey Belousov 
wrote:

> Hi Rajesh <https://plus.google.com/u/0/114088226284364321936?prsrc=4>
>
> Do you have any timeline on where we would be able to have RC01 for a
> test-drive?
>
> Thank you
>
> On Sun, May 10, 2015 at 9:52 AM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> >
> >
>

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC1

[rajeshb...@apache.org]

@Gabriel,
bq. The format that the checksums are written in here makes it
impossible to check them with an automated tool, which is a bit of an
issue for me and perhaps a bigger issue for people who count on that
working for all software downloads. Any reason for the change?

Sorry for this. When I read
https://www.apache.org/dev/openpgp.html#generate-key this link
I thought it's fine to have install gpg2 or gpg and went to install gpg2.
Didn't realize this problem.
Next time make release with gpg.

Thanks,
Rajeshbabu.


On Thu, May 14, 2015 at 9:08 AM, Enis Söztutar  wrote:

> Here is my +1.
>
> Verified sigs, crcs.
> Run with HBase-1.0.1 local mode.
> Tried the examples.
> checked directory layouts, jars
> checked src tarball contents vs tag
>
> +1 to what Gabriel says.
> Enis
>
>
>
>
> On Tue, May 12, 2015 at 1:04 PM, Gabriel Reid 
> wrote:
>
> > +1 to release. I ran the same checks and ran into the same issues as
> > with the HBase-0.98 variant, which I'm reposting below for
> > completeness.
> >
> > * Verified the checksums and signatures, they all match up, but I
> > noticed that they were created differently (using gpg2) than previous
> > releases. The format that the checksums are written in here makes it
> > impossible to check them with an automated tool, which is a bit of an
> > issue for me and perhaps a bigger issue for people who count on that
> > working for all software downloads. Any reason for the change?
> > * I successfully ran the full integration test suite, although it took
> > a few tries due to failures on
> > org.apache.phoenix.pherf.ResultTest#testMonitorResult. I've logged
> > this in JIRA (PHOENIX-1963)
> > * I successfully ran rat, although initially ran into some issues with
> > artifacts that were left over from the previous build and not cleaned
> > up by 'mvn clean', logged in PHOENIX-1964
> > * I attempted to verify that the contents of the tag
> > (v4.4.0-HBase-0.98-rc1) are identical to the contents of the source
> > distribution, and noticed that they aren't -- the make_rc.sh script is
> > different between these two (it includes among other things the
> > changed checksum calculation). This isn't enough to sink this build,
> > but it's something we should try to avoid in the future.
> >
> > - Gabriel
> >
> > On Tue, May 12, 2015 at 2:41 AM, rajeshb...@apache.org
> >  wrote:
> > > Hi Everyone,
> > >
> > > This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.0 RC1. This
> is
> > the
> > > next minor release of Phoenix 4, compatible with the 1.0(branch of
> > > Apache HBase(1.0.1+) . The release includes both a source-only release
> > and a
> > > convenience binary release.
> > >
> > > The 4.4.0-HBase-1.0 release has feature parity with our pending
> > > 4.4.0-HBase-0.98 release.  New features include:
> > > - Support HBase HA Query(timeline-consistent region replica read)[1]
> > > - Alter session query support(at present changing query consistency
> > level.
> > > Can be used for changing connection properties.)
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc1/src/
> > >
> > > The binary artifacts can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.0-rc1/bin/
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=09d1840876d7b55e32d753b541eb7df22b85
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.0-rc1
> > >
> > > Vote will be open for at least 72 hours. Please vote:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > The Apache Phoenix Team
> > >
> > > [1] https://issues.apache.org/jira/browse/PHOENIX-1683
> >
>

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC1

[rajeshb...@apache.org]

Here is my +1.

- verified signing key for src and bin tgzs
- extracted src tgz and ran full integration tests and it passed.
- ran apache-rat check no issues reported.
- installed HBase 1.0.1 in standalone mode and ran examples and no issues.
- loaded some data and created indexes and things are fine.
- created tables with replicas and tested HBase HA it's working fine.
- tested UDFs and things are fine but hadoop jars(needed for dynamically
loading the udf jars) should be placed in phoenix-assembly/target folder in
phoenix home. Raised PHOENIX-1977 clean up it. It's not critical and should
not sink the RC.
- started query server and ran some queries from sqlline-thin command line.
They are fine.
- enabled tracing and ran some queries and checked the trace information
for the queries. It's fine.

Thanks,
Rajeshbabu.



On Sat, May 16, 2015 at 1:11 AM, James Taylor 
wrote:

> +1. Ran same tests as with 0.98 release.
>
> On Thu, May 14, 2015 at 6:34 PM, Nick Dimiduk  wrote:
> > I think which version of gpg used is not important, so long as the
> > signatures are valid and can be consumed universally. Likewise with the
> > checksum calculations. I agree that standardizing on this for the project
> > would be helpful for all parties, but until we enforce generating release
> > artifacts in jenkins, I think discrepancies between release managers is
> > acceptable. I do find it startling that there's a difference between
> what's
> > on the tag and what's in the tgz, but since it's not product changes,
> only
> > dev tools, it's not enough to sink the RC.
> >
> > Now for my +1
> >
> > - verified signing key for both tgzs
> > - run with 1.0.1 and checkout of branch-1.0/HEAD in local mode
> > - create table, load example data with psql, list tables and content
> > - start query server and perform similar experiments there; everything
> > works as expected and log levels look good
> > - checked src tgzl with apache-rat:check, and verified no .class, .jar,
> > .orig, ~ files present
> > - build src tgz, UT all pass (with PHOENIX-1963 applied, thanks Gabriel.
> > Missing a close() in test is not bad enough to sink the RC.)
> >
> > On Wed, May 13, 2015 at 9:10 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> @Gabriel,
> >> bq. The format that the checksums are written in here makes it
> >> impossible to check them with an automated tool, which is a bit of an
> >> issue for me and perhaps a bigger issue for people who count on that
> >> working for all software downloads. Any reason for the change?
> >>
> >> Sorry for this. When I read
> >> https://www.apache.org/dev/openpgp.html#generate-key this link
> >> I thought it's fine to have install gpg2 or gpg and went to install
> gpg2.
> >> Didn't realize this problem.
> >> Next time make release with gpg.
> >>
> >> Thanks,
> >> Rajeshbabu.
> >>
> >>
> >> On Thu, May 14, 2015 at 9:08 AM, Enis Söztutar  wrote:
> >>
> >> > Here is my +1.
> >> >
> >> > Verified sigs, crcs.
> >> > Run with HBase-1.0.1 local mode.
> >> > Tried the examples.
> >> > checked directory layouts, jars
> >> > checked src tarball contents vs tag
> >> >
> >> > +1 to what Gabriel says.
> >> > Enis
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, May 12, 2015 at 1:04 PM, Gabriel Reid  >
> >> > wrote:
> >> >
> >> > > +1 to release. I ran the same checks and ran into the same issues as
> >> > > with the HBase-0.98 variant, which I'm reposting below for
> >> > > completeness.
> >> > >
> >> > > * Verified the checksums and signatures, they all match up, but I
> >> > > noticed that they were created differently (using gpg2) than
> previous
> >> > > releases. The format that the checksums are written in here makes it
> >> > > impossible to check them with an automated tool, which is a bit of
> an
> >> > > issue for me and perhaps a bigger issue for people who count on that
> >> > > working for all software downloads. Any reason for the change?
> >> > > * I successfully ran the full integration test suite, although it
> took
> >> > > a few tries due to failures on
> >> > > org.apache.phoenix.pherf.ResultTest#testMonitorResult. I've logged
> >> > > this in JIRA (PHOENIX-1963)
> >> 

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC1

[rajeshb...@apache.org]

Here is my +1.

- verified signing key for src and bin tgzs
- extracted src tgz and ran full integration tests and it passed.
- ran apache-rat check no issues reported.
- installed HBase 0.98.12 in standalone mode and ran examples and no issues.
- loaded some data and created indexes and things are fine.
- tested UDFs and things are fine but hadoop jars(needed for dynamically
loading the udf jars) should be placed in phoenix-assembly/target folder in
phoenix home. Raised PHOENIX-1977 clean up it. It's not critical and should
not sink the RC.
- started query server and ran some queries from sqlline-thin command line.
They are fine.
- enabled tracing and ran some queries and checked the trace information
for the queries. It's fine.

Thanks,
Rajeshbabu.

On Sat, May 16, 2015 at 1:11 AM, James Taylor 
wrote:

> +1
>
> - verified basic installation and querying worked
> - verified creating mutable secondary indexes worked
> - verified various DDL calls worked
>
> On Fri, May 15, 2015 at 10:30 AM, Nick Dimiduk 
> wrote:
> > I've already given my opinion on gpg versions, checksums formats, and the
> > delta between tag and packaging on the other thread.
> >
> > For this release, +1:
> >
> > - verified signing key for both tgzs
> > - run with 0.98.12 in local mode
> > - create table, load example data with psql, list tables and content
> > - start query server and perform similar experiments there; everything
> > works as expected and log levels look good
> > - checked src tgzl with apache-rat:check, and verified no .class, .jar,
> > .orig, ~ files present
> > - build src tgz, UT all pass (no need for PHOENIX-1963 this round).
> >
> > On Mon, May 11, 2015 at 5:29 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> Hi Everyone,
> >>
> >> This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC1. This
> is
> >> the
> >> next minor release of Phoenix 4, compatible with the 0.98 branch of
> >> Apache HBase. The release includes both a source-only release and a
> >> convenience binary release.
> >>
> >> Highlights of the release include:
> >> - spark integration[1]
> >> - query server[2]
> >> - 7.5x performance improvement for non aggregate, unordered queries[3]
> >> - pherf - load tester measures throughput[4]
> >> - support union All and union queries in subquery
> >>(PHOENIX-1580,PHOENIX-1807).
> >> - support for user defined functions(PHOENIX-538)
> >> - many math and date/time buit-in functions
> >>(PHOENIX-1662, PHOENIX-1660)
> >> - mr job to populate indexes(PHOENIX-1609)
> >> - improvements in tracing and monitoring.
> >> - some more improvements in CBO
> >> - over 70 bug fixes and etc...
> >>
> >> For a complete list of changes, see:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
> >>
> >> The source tarball, including signatures, digests, etc can be found at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/src/
> >>
> >>
> >> The binary artifacts can be found at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/bin/
> >>
> >>
> >> Release artifacts are signed with the following key:
> >> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >>
> >> The hash and tag to be voted upon:
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=4126cb3f7e5fcd69ba03e2fb24778ec47051c39b
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc1
> >>
> >> Vote will be open for at least 72 hours. Please vote:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >> Thanks,
> >> The Apache Phoenix Team
> >>
> >> [1] http://phoenix.apache.org/phoenix_spark.html
> >> [2] http://phoenix.apache.org/server.html
> >> <http://phoenix.apache.org/server.html>
> >> [3] https://issues.apache.org/jira/browse/PHOENIX-1779
> >> [4] http://phoenix.apache.org/pherf.html
> >>
>

[RESULT][VOTE] Release of Apache Phoenix 4.4.0-HBase-1.0 RC1

[rajeshb...@apache.org]

The vote has passed with 5 binding +1 votes and no 0's. I will publish the
release artifacts shortly. Thanks everyone for helping with the release!

Thanks,
Rajeshbabu.

On Mon, May 18, 2015 at 12:36 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Here is my +1.
>
> - verified signing key for src and bin tgzs
> - extracted src tgz and ran full integration tests and it passed.
> - ran apache-rat check no issues reported.
> - installed HBase 1.0.1 in standalone mode and ran examples and no issues.
> - loaded some data and created indexes and things are fine.
> - created tables with replicas and tested HBase HA it's working fine.
> - tested UDFs and things are fine but hadoop jars(needed for dynamically
> loading the udf jars) should be placed in phoenix-assembly/target folder in
> phoenix home. Raised PHOENIX-1977 clean up it. It's not critical and should
> not sink the RC.
> - started query server and ran some queries from sqlline-thin command
> line. They are fine.
> - enabled tracing and ran some queries and checked the trace information
> for the queries. It's fine.
>
> Thanks,
> Rajeshbabu.
>
>
>
> On Sat, May 16, 2015 at 1:11 AM, James Taylor 
> wrote:
>
>> +1. Ran same tests as with 0.98 release.
>>
>> On Thu, May 14, 2015 at 6:34 PM, Nick Dimiduk 
>> wrote:
>> > I think which version of gpg used is not important, so long as the
>> > signatures are valid and can be consumed universally. Likewise with the
>> > checksum calculations. I agree that standardizing on this for the
>> project
>> > would be helpful for all parties, but until we enforce generating
>> release
>> > artifacts in jenkins, I think discrepancies between release managers is
>> > acceptable. I do find it startling that there's a difference between
>> what's
>> > on the tag and what's in the tgz, but since it's not product changes,
>> only
>> > dev tools, it's not enough to sink the RC.
>> >
>> > Now for my +1
>> >
>> > - verified signing key for both tgzs
>> > - run with 1.0.1 and checkout of branch-1.0/HEAD in local mode
>> > - create table, load example data with psql, list tables and content
>> > - start query server and perform similar experiments there; everything
>> > works as expected and log levels look good
>> > - checked src tgzl with apache-rat:check, and verified no .class, .jar,
>> > .orig, ~ files present
>> > - build src tgz, UT all pass (with PHOENIX-1963 applied, thanks Gabriel.
>> > Missing a close() in test is not bad enough to sink the RC.)
>> >
>> > On Wed, May 13, 2015 at 9:10 PM, rajeshb...@apache.org <
>> > chrajeshbab...@gmail.com> wrote:
>> >
>> >> @Gabriel,
>> >> bq. The format that the checksums are written in here makes it
>> >> impossible to check them with an automated tool, which is a bit of an
>> >> issue for me and perhaps a bigger issue for people who count on that
>> >> working for all software downloads. Any reason for the change?
>> >>
>> >> Sorry for this. When I read
>> >> https://www.apache.org/dev/openpgp.html#generate-key this link
>> >> I thought it's fine to have install gpg2 or gpg and went to install
>> gpg2.
>> >> Didn't realize this problem.
>> >> Next time make release with gpg.
>> >>
>> >> Thanks,
>> >> Rajeshbabu.
>> >>
>> >>
>> >> On Thu, May 14, 2015 at 9:08 AM, Enis Söztutar 
>> wrote:
>> >>
>> >> > Here is my +1.
>> >> >
>> >> > Verified sigs, crcs.
>> >> > Run with HBase-1.0.1 local mode.
>> >> > Tried the examples.
>> >> > checked directory layouts, jars
>> >> > checked src tarball contents vs tag
>> >> >
>> >> > +1 to what Gabriel says.
>> >> > Enis
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, May 12, 2015 at 1:04 PM, Gabriel Reid <
>> gabriel.r...@gmail.com>
>> >> > wrote:
>> >> >
>> >> > > +1 to release. I ran the same checks and ran into the same issues
>> as
>> >> > > with the HBase-0.98 variant, which I'm reposting below for
>> >> > > completeness.
>> >> > >
>> >> > > * Verified the checksums and signatures, they all match up, but I
>> >> > > noticed 

[RESULT][VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC1

[rajeshb...@apache.org]

The vote has passed with 5 binding +1 votes and no 0's. I will publish the
release artifacts shortly. Thanks everyone for helping with the release!

Thanks,
Rajeshbabu.

-- Forwarded message --
From: rajeshb...@apache.org 
Date: Mon, May 18, 2015 at 12:41 AM
Subject: Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-0.98 RC1
To: "dev@phoenix.apache.org" 


Here is my +1.

- verified signing key for src and bin tgzs
- extracted src tgz and ran full integration tests and it passed.
- ran apache-rat check no issues reported.
- installed HBase 0.98.12 in standalone mode and ran examples and no issues.
- loaded some data and created indexes and things are fine.
- tested UDFs and things are fine but hadoop jars(needed for dynamically
loading the udf jars) should be placed in phoenix-assembly/target folder in
phoenix home. Raised PHOENIX-1977 clean up it. It's not critical and should
not sink the RC.
- started query server and ran some queries from sqlline-thin command line.
They are fine.
- enabled tracing and ran some queries and checked the trace information
for the queries. It's fine.

Thanks,
Rajeshbabu.

On Sat, May 16, 2015 at 1:11 AM, James Taylor 
wrote:

> +1
>
> - verified basic installation and querying worked
> - verified creating mutable secondary indexes worked
> - verified various DDL calls worked
>
> On Fri, May 15, 2015 at 10:30 AM, Nick Dimiduk 
> wrote:
> > I've already given my opinion on gpg versions, checksums formats, and the
> > delta between tag and packaging on the other thread.
> >
> > For this release, +1:
> >
> > - verified signing key for both tgzs
> > - run with 0.98.12 in local mode
> > - create table, load example data with psql, list tables and content
> > - start query server and perform similar experiments there; everything
> > works as expected and log levels look good
> > - checked src tgzl with apache-rat:check, and verified no .class, .jar,
> > .orig, ~ files present
> > - build src tgz, UT all pass (no need for PHOENIX-1963 this round).
> >
> > On Mon, May 11, 2015 at 5:29 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> Hi Everyone,
> >>
> >> This is a call for a vote on Apache Phoenix 4.4.0-HBase-0.98 RC1. This
> is
> >> the
> >> next minor release of Phoenix 4, compatible with the 0.98 branch of
> >> Apache HBase. The release includes both a source-only release and a
> >> convenience binary release.
> >>
> >> Highlights of the release include:
> >> - spark integration[1]
> >> - query server[2]
> >> - 7.5x performance improvement for non aggregate, unordered queries[3]
> >> - pherf - load tester measures throughput[4]
> >> - support union All and union queries in subquery
> >>(PHOENIX-1580,PHOENIX-1807).
> >> - support for user defined functions(PHOENIX-538)
> >> - many math and date/time buit-in functions
> >>(PHOENIX-1662, PHOENIX-1660)
> >> - mr job to populate indexes(PHOENIX-1609)
> >> - improvements in tracing and monitoring.
> >> - some more improvements in CBO
> >> - over 70 bug fixes and etc...
> >>
> >> For a complete list of changes, see:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
> >>
> >> The source tarball, including signatures, digests, etc can be found at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/src/
> >>
> >>
> >> The binary artifacts can be found at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-0.98_rc1/bin/
> >>
> >>
> >> Release artifacts are signed with the following key:
> >> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >>
> >> The hash and tag to be voted upon:
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=4126cb3f7e5fcd69ba03e2fb24778ec47051c39b
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-0.98-rc1
> >>
> >> Vote will be open for at least 72 hours. Please vote:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >> Thanks,
> >> The Apache Phoenix Team
> >>
> >> [1] http://phoenix.apache.org/phoenix_spark.html
> >> [2] http://phoenix.apache.org/server.html
> >> <http://phoenix.apache.org/server.html>
> >> [3] https://issues.apache.org/jira/browse/PHOENIX-1779
> >> [4] http://phoenix.apache.org/pherf.html
> >>
>

I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well

[rajeshb...@apache.org]

Hi,

Already HBase-1.1.0 released and we already have patch to support with
it(PHOENIX-1763). I feel we can release 4.4.0 with HBase-1.1.0 as well.

What do you guys say?

Thanks,
Rajeshbabu.

Re: [jira] [Commented] (PHOENIX-1976) Improve PhoenixDriver registration when addShutdownHook fails

[rajeshb...@apache.org]

If it's committed to 4.x branches it should be fine as of now.

On Tue, May 19, 2015 at 6:31 AM, Nick Dimiduk (JIRA) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/PHOENIX-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549598#comment-14549598
> ]
>
> Nick Dimiduk commented on PHOENIX-1976:
> ---
>
> You want this for 4.4.1, [~chrajeshbab...@gmail.com]? Let me know where I
> can apply it. Thanks.
>
> > Improve PhoenixDriver registration when addShutdownHook fails
> > -
> >
> > Key: PHOENIX-1976
> > URL: https://issues.apache.org/jira/browse/PHOENIX-1976
> > Project: Phoenix
> >  Issue Type: Bug
> >Reporter: Josh Elser
> >Assignee: Josh Elser
> >Priority: Minor
> > Fix For: 5.0.0, 4.5.0
> >
> > Attachments: PHOENIX-1976-master.patch
> >
> >
> > Noticed this in running some tests. RegionServer was shutting down and
> MetaDataRegionObserver was just invoking {{postOpen}}
> > When the {{Class.forName(PhoenixDriver.class.getName())}} gets called,
> the static initializer in {{PhoenixDriver}} gets invoked. Because the
> RegionServer is already stopping, the {{addShutdownHook}} fails with an
> {{IllegalArgumentException}}.
> > It's not a _huge_ concern because we know the JVM is going down, but
> there are a few things we could handle better:
> > * Ensure the PhoenixDriver gets closed if the shutdown hook fails to
> register
> > * Avoid registering the PhoenixDriver instance if we're shutting down
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well

[rajeshb...@apache.org]

James,

bq. Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
against an HBase 1.1 running Phoenix?
Mostly they should work. I will quickly check this today.

bq.  Has Andy's patch already been applied for using
the new RS interfaces?
The patch at PHOENIX-1763 has required changes after new RS interface
changes.

Thanks,
Rajeshbabu

On Tue, May 19, 2015 at 11:32 PM, James Taylor 
wrote:

> Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
> against an HBase 1.1 running Phoenix? If no, we'll need to release
> this in a 5.0 version. Has Andy's patch already been applied for using
> the new RS interfaces?
>
> Thanks,
> James
>
> On Tue, May 19, 2015 at 10:30 AM, rajeshb...@apache.org
>  wrote:
> > Hi,
> >
> > Already HBase-1.1.0 released and we already have patch to support with
> > it(PHOENIX-1763). I feel we can release 4.4.0 with HBase-1.1.0 as well.
> >
> > What do you guys say?
> >
> > Thanks,
> > Rajeshbabu.
>

Re: I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well

[rajeshb...@apache.org]

James,

I have installed HBase 1.1.0 with phoenix-4.4.0-HBase-1.0 rc1 +
PHOENIX-1763 patch at server side. Created tables,indexes,uploaded data
with performance script from the new client and performed reads/writes from
all old clients of versions 4.1.0,4.2.2 and 4.3.1. No issues found.

So I feel we can release with HBase-1.1.0. Running test suite and seems
fine.

Thanks,
Rajeshbabu.


On Wed, May 20, 2015 at 7:05 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> James,
>
> bq. Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
> against an HBase 1.1 running Phoenix?
> Mostly they should work. I will quickly check this today.
>
> bq.  Has Andy's patch already been applied for using
> the new RS interfaces?
> The patch at PHOENIX-1763 has required changes after new RS interface
> changes.
>
> Thanks,
> Rajeshbabu
>
> On Tue, May 19, 2015 at 11:32 PM, James Taylor 
> wrote:
>
>> Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
>> against an HBase 1.1 running Phoenix? If no, we'll need to release
>> this in a 5.0 version. Has Andy's patch already been applied for using
>> the new RS interfaces?
>>
>> Thanks,
>> James
>>
>> On Tue, May 19, 2015 at 10:30 AM, rajeshb...@apache.org
>>  wrote:
>> > Hi,
>> >
>> > Already HBase-1.1.0 released and we already have patch to support with
>> > it(PHOENIX-1763). I feel we can release 4.4.0 with HBase-1.1.0 as well.
>> >
>> > What do you guys say?
>> >
>> > Thanks,
>> > Rajeshbabu.
>>
>
>

Re: I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well

[rajeshb...@apache.org]

Thanks James. Sure I will run it also.

Here is my plan for the release:

1) create the 4.x-HBase-1.1 branch from latest 4.x-HBase-1.0
2) change the hbase version to 1.1.0 and commit PHOENIX-1793
3) Setup jenkins for the branch to run the test suite.
3) cut rc from 4.x-HBase-1.1
4) before vote is going to pass create 4.4-HBase-1.1 branch for 4.4.x bug
fix releases.

I

Thanks,
Rajeshbabu.


On Thu, May 21, 2015 at 9:52 PM, James Taylor 
wrote:

> Hi Rajeshbabu,
> Sounds good. Probably a good idea to run our perf regression suite to
> get an idea of performance too. I'm fine with a release, though.
> Thanks,
> James
>
> On Thu, May 21, 2015 at 6:09 AM, rajeshb...@apache.org
>  wrote:
> > James,
> >
> > I have installed HBase 1.1.0 with phoenix-4.4.0-HBase-1.0 rc1 +
> > PHOENIX-1763 patch at server side. Created tables,indexes,uploaded data
> > with performance script from the new client and performed reads/writes
> from
> > all old clients of versions 4.1.0,4.2.2 and 4.3.1. No issues found.
> >
> > So I feel we can release with HBase-1.1.0. Running test suite and seems
> > fine.
> >
> > Thanks,
> > Rajeshbabu.
> >
> >
> > On Wed, May 20, 2015 at 7:05 AM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> James,
> >>
> >> bq. Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
> >> against an HBase 1.1 running Phoenix?
> >> Mostly they should work. I will quickly check this today.
> >>
> >> bq.  Has Andy's patch already been applied for using
> >> the new RS interfaces?
> >> The patch at PHOENIX-1763 has required changes after new RS interface
> >> changes.
> >>
> >> Thanks,
> >> Rajeshbabu
> >>
> >> On Tue, May 19, 2015 at 11:32 PM, James Taylor 
> >> wrote:
> >>
> >>> Will older Phoenix 4.x clients work with the new Phoenix 4.4 clients
> >>> against an HBase 1.1 running Phoenix? If no, we'll need to release
> >>> this in a 5.0 version. Has Andy's patch already been applied for using
> >>> the new RS interfaces?
> >>>
> >>> Thanks,
> >>> James
> >>>
> >>> On Tue, May 19, 2015 at 10:30 AM, rajeshb...@apache.org
> >>>  wrote:
> >>> > Hi,
> >>> >
> >>> > Already HBase-1.1.0 released and we already have patch to support
> with
> >>> > it(PHOENIX-1763). I feel we can release 4.4.0 with HBase-1.1.0 as
> well.
> >>> >
> >>> > What do you guys say?
> >>> >
> >>> > Thanks,
> >>> > Rajeshbabu.
> >>>
> >>
> >>
>

All clear

[rajeshb...@apache.org]

I have created branches 4.4-HBase-0.98 branch off of the 4.x-HBase-0.98
branch that matches the point at which the release was cut. Similarly
created  4.4-HBase-1.0 off of the 4.x-HBase-1.0.

Only bug fixes need to be committed for 4.4-HBase-0.98 and 4.4-HBase-1.0
branches.
Please let me know before commiting. If any critical issue don't wait for
me go and commit.

If any bug fixes committed to 4.x versions or master after RC please port
them for these releases.

Thanks,
Rajeshbabu.

Re: I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well

[rajeshb...@apache.org]

Makes sense Nick. Cut the new branch from 4.4.0-HBase-1.0 tag.

Thanks,
Rajeshbabu.

On Fri, May 22, 2015 at 5:58 AM, Nick Dimiduk  wrote:

> This looks good except for (1) branch should be cut from the
> 4.4.0-HBase-1.0 tag. That way 4.4.0 will be feature-identical across all
> releases. Then we'll need to go back over what's landed on 4.x-HBase-1.0
> since 4.4.0 was released and bring forward any patches, so that all 3
> branches are aligned for 4.4.1.
>
> Make sense?
>
> On Thu, May 21, 2015 at 1:35 PM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > Thanks James. Sure I will run it also.
> >
> > Here is my plan for the release:
> >
> > 1) create the 4.x-HBase-1.1 branch from latest 4.x-HBase-1.0
> > 2) change the hbase version to 1.1.0 and commit PHOENIX-1793
> > 3) Setup jenkins for the branch to run the test suite.
> > 3) cut rc from 4.x-HBase-1.1
> > 4) before vote is going to pass create 4.4-HBase-1.1 branch for 4.4.x bug
> > fix releases.
> >
> > I
> >
> > Thanks,
> > Rajeshbabu.
> >
> >
> > On Thu, May 21, 2015 at 9:52 PM, James Taylor 
> > wrote:
> >
> > > Hi Rajeshbabu,
> > > Sounds good. Probably a good idea to run our perf regression suite to
> > > get an idea of performance too. I'm fine with a release, though.
> > > Thanks,
> > > James
> > >
> > > On Thu, May 21, 2015 at 6:09 AM, rajeshb...@apache.org
> > >  wrote:
> > > > James,
> > > >
> > > > I have installed HBase 1.1.0 with phoenix-4.4.0-HBase-1.0 rc1 +
> > > > PHOENIX-1763 patch at server side. Created tables,indexes,uploaded
> data
> > > > with performance script from the new client and performed
> reads/writes
> > > from
> > > > all old clients of versions 4.1.0,4.2.2 and 4.3.1. No issues found.
> > > >
> > > > So I feel we can release with HBase-1.1.0. Running test suite and
> seems
> > > > fine.
> > > >
> > > > Thanks,
> > > > Rajeshbabu.
> > > >
> > > >
> > > > On Wed, May 20, 2015 at 7:05 AM, rajeshb...@apache.org <
> > > > chrajeshbab...@gmail.com> wrote:
> > > >
> > > >> James,
> > > >>
> > > >> bq. Will older Phoenix 4.x clients work with the new Phoenix 4.4
> > clients
> > > >> against an HBase 1.1 running Phoenix?
> > > >> Mostly they should work. I will quickly check this today.
> > > >>
> > > >> bq.  Has Andy's patch already been applied for using
> > > >> the new RS interfaces?
> > > >> The patch at PHOENIX-1763 has required changes after new RS
> interface
> > > >> changes.
> > > >>
> > > >> Thanks,
> > > >> Rajeshbabu
> > > >>
> > > >> On Tue, May 19, 2015 at 11:32 PM, James Taylor <
> > jamestay...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Will older Phoenix 4.x clients work with the new Phoenix 4.4
> clients
> > > >>> against an HBase 1.1 running Phoenix? If no, we'll need to release
> > > >>> this in a 5.0 version. Has Andy's patch already been applied for
> > using
> > > >>> the new RS interfaces?
> > > >>>
> > > >>> Thanks,
> > > >>> James
> > > >>>
> > > >>> On Tue, May 19, 2015 at 10:30 AM, rajeshb...@apache.org
> > > >>>  wrote:
> > > >>> > Hi,
> > > >>> >
> > > >>> > Already HBase-1.1.0 released and we already have patch to support
> > > with
> > > >>> > it(PHOENIX-1763). I feel we can release 4.4.0 with HBase-1.1.0 as
> > > well.
> > > >>> >
> > > >>> > What do you guys say?
> > > >>> >
> > > >>> > Thanks,
> > > >>> > Rajeshbabu.
> > > >>>
> > > >>
> > > >>
> > >
> >
>

[ANNOUNCE] Apache Phoenix 4.4-0-HBase-0.98 released

[rajeshb...@apache.org]

The Apache Phoenix team is pleased to announce the immediate
availability of the 4.4.0-HBase-0.98 release compatible with HBase 0.98.x.
Highlights include:

- spark integration[1]
- query server[2]
- support for user defined functions[3]
- pherf - load tester measures throughput[4]
- support union All and union queries in subquery[5].
- 7.5x performance improvement for non aggregate, unordered queries
- many math and date/time buit-in functions
- mr job to populate indexes
- improvements in tracing and monitoring.
- some more improvements in CBO
- over 70 bug fixes and etc...

The release is available through maven or may be downloaded here [6].

Thanks to all the contributors who made this release possible!

Regards,
The Apache Phoenix Team

[1] http://phoenix.apache.org/phoenix_spark.html
[2] http://phoenix.apache.org/server.html
[3] http://phoenix.apache.org/udf.html
[4] http://phoenix.apache.org/pherf.html
[5] http://phoenix.apache.org/language/index.html#select
[6] http://phoenix.apache.org/download.html

[ANNOUNCE] Apache Phoenix 4.4-0-HBase-1.0 released

[rajeshb...@apache.org]

The Apache Phoenix team is pleased to announce the immediate
availability of the 4.4.0-HBase-1.0 release compatible with HBase
1.0.x(1.0.1+).

The 4.4.0-HBase-1.0 release has feature parity with our 4.4.0-HBase-0.98
release.

Extra features include:
- support HBase HA Query(timeline-consistent region replica read)[1]
- alter session query support

The release is available through maven or may be downloaded here[2].

Thanks to all the contributors who made this release possible!

Regards,
The Apache Phoenix Team

[1] https://issues.apache.org/jira/browse/PHOENIX-1683
[2] http://phoenix.apache.org/download.html

I will make rc tonight IST(I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well)

[rajeshb...@apache.org]

I ran the tests multiple times locally and they are always passing.

[INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
phoenix-assembly ---
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Phoenix . SUCCESS [
 1.531 s]
[INFO] Phoenix Core ... SUCCESS [49:22
min]
[INFO] Phoenix - Flume  SUCCESS [01:09
min]
[INFO] Phoenix - Pig .. SUCCESS [03:04
min]
[INFO] Phoenix Query Server Client  SUCCESS [
 0.469 s]
[INFO] Phoenix Query Server ... SUCCESS [01:47
min]
[INFO] Phoenix - Pherf  SUCCESS [01:05
min]
[INFO] Phoenix - Spark  SUCCESS [
 3.735 s]
[INFO] Phoenix Assembly ... SUCCESS [
21.070 s]
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 56:57 min
[INFO] Finished at: 2015-05-24T14:21:52+05:30

The reason for failures in Jenkings might be HBase 1.1.0 jars are older
ones of it's RCs so getting linkage errors.
Once we remove them from local repository then it will download latest jars
and the tests should pass.
Any one have an idea how to remove the jars form local repository of
jenkins machines?

Even with -U for mvn it's not downloading the latest jars.
By the time will compare performance with other versions.

Thanks,
Rajeshbabu.

On Fri, May 22, 2015 at 1:07 PM, Enis Söztutar  wrote:

> I have pushed PHOENIX-1763 and PHOENIX-1681 to master, 4.4-HBase-1.1, and
> 4.x-HBase-1.1 branches.
>
> I think one unit test is failing (IndexToolIT) which Rajesh is taking a
> look.
>
> Enis
>
> On Thu, May 21, 2015 at 6:38 PM, Enis Söztutar  wrote:
>
> > Makes sense.
> >
> > +1 for cutting the RC from the 4.4 release tag. So in your above plan, I
> > would change step 3 into:
> >  (3) Create the 4.4-branch from 4.4.0-HBase-1.0 tag
> >
> > Then we can commit PHOENIX-1763 and PHOENIX-1681 to 4.4-HBase-1.1,
> > 4.x-HBase-1.1 and master.
> >
> > For Phoenix master branch, and 4.5 releases, I think we can drop
> HBase-1.0
> > support if we think that there is a lot of overhead. HBase-1.1 is rolling
> > upgradable and compatible with 1.0, so users should not be stuck with it
> > for a long time. it is a matter of overhead of keeping one extra branch
> and
> > release vs whether we would want to support Hbase-1.0 users for 4.5+.
> Just
> > my 2 cents.
> >
> > Enis
> >
> > On Thu, May 21, 2015 at 5:39 PM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> >> Makes sense Nick. Cut the new branch from 4.4.0-HBase-1.0 tag.
> >>
> >> Thanks,
> >> Rajeshbabu.
> >>
> >> On Fri, May 22, 2015 at 5:58 AM, Nick Dimiduk 
> wrote:
> >>
> >> > This looks good except for (1) branch should be cut from the
> >> > 4.4.0-HBase-1.0 tag. That way 4.4.0 will be feature-identical across
> all
> >> > releases. Then we'll need to go back over what's landed on
> 4.x-HBase-1.0
> >> > since 4.4.0 was released and bring forward any patches, so that all 3
> >> > branches are aligned for 4.4.1.
> >> >
> >> > Make sense?
> >> >
> >> > On Thu, May 21, 2015 at 1:35 PM, rajeshb...@apache.org <
> >> > chrajeshbab...@gmail.com> wrote:
> >> >
> >> > > Thanks James. Sure I will run it also.
> >> > >
> >> > > Here is my plan for the release:
> >> > >
> >> > > 1) create the 4.x-HBase-1.1 branch from latest 4.x-HBase-1.0
> >> > > 2) change the hbase version to 1.1.0 and commit PHOENIX-1793
> >> > > 3) Setup jenkins for the branch to run the test suite.
> >> > > 3) cut rc from 4.x-HBase-1.1
> >> > > 4) before vote is going to pass create 4.4-HBase-1.1 branch for
> 4.4.x
> >> bug
> >> > > fix releases.
> >> > >
> >> > > I
> >> > >
> >> > > Thanks,
> >> > > Rajeshbabu.
> >> > >
> >> > >
> >> > > On Thu, May 21, 2015 at 9:52 PM, James Taylor <
> jamestay...@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > Hi Rajeshbabu,
> >> > > > Sounds good. Probab

Re: I will make rc tonight IST(I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well)

[rajeshb...@apache.org]

Hi Ted,

Tests are failing for both the branches and master branch as well.

Thanks,
Rajeshbabu.
On May 24, 2015 7:21 PM, "Ted Yu"  wrote:

> Did the test fail on branch 4.4-HBase-1.1, branch 4.x-HBase-1.1 or both ?
>
> Cheers
>
> On Sun, May 24, 2015 at 2:38 AM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > I ran the tests multiple times locally and they are always passing.
> >
> > [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
> > phoenix-assembly ---
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Phoenix . SUCCESS [
> >  1.531 s]
> > [INFO] Phoenix Core ... SUCCESS
> [49:22
> > min]
> > [INFO] Phoenix - Flume  SUCCESS
> [01:09
> > min]
> > [INFO] Phoenix - Pig .. SUCCESS
> [03:04
> > min]
> > [INFO] Phoenix Query Server Client  SUCCESS [
> >  0.469 s]
> > [INFO] Phoenix Query Server ... SUCCESS
> [01:47
> > min]
> > [INFO] Phoenix - Pherf  SUCCESS
> [01:05
> > min]
> > [INFO] Phoenix - Spark  SUCCESS [
> >  3.735 s]
> > [INFO] Phoenix Assembly ... SUCCESS [
> > 21.070 s]
> > [INFO]
> > 
> > [INFO] BUILD SUCCESS
> > [INFO]
> > 
> > [INFO] Total time: 56:57 min
> > [INFO] Finished at: 2015-05-24T14:21:52+05:30
> >
> > The reason for failures in Jenkings might be HBase 1.1.0 jars are older
> > ones of it's RCs so getting linkage errors.
> > Once we remove them from local repository then it will download latest
> jars
> > and the tests should pass.
> > Any one have an idea how to remove the jars form local repository of
> > jenkins machines?
> >
> > Even with -U for mvn it's not downloading the latest jars.
> > By the time will compare performance with other versions.
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Fri, May 22, 2015 at 1:07 PM, Enis Söztutar  wrote:
> >
> > > I have pushed PHOENIX-1763 and PHOENIX-1681 to master, 4.4-HBase-1.1,
> and
> > > 4.x-HBase-1.1 branches.
> > >
> > > I think one unit test is failing (IndexToolIT) which Rajesh is taking a
> > > look.
> > >
> > > Enis
> > >
> > > On Thu, May 21, 2015 at 6:38 PM, Enis Söztutar 
> wrote:
> > >
> > > > Makes sense.
> > > >
> > > > +1 for cutting the RC from the 4.4 release tag. So in your above
> plan,
> > I
> > > > would change step 3 into:
> > > >  (3) Create the 4.4-branch from 4.4.0-HBase-1.0 tag
> > > >
> > > > Then we can commit PHOENIX-1763 and PHOENIX-1681 to 4.4-HBase-1.1,
> > > > 4.x-HBase-1.1 and master.
> > > >
> > > > For Phoenix master branch, and 4.5 releases, I think we can drop
> > > HBase-1.0
> > > > support if we think that there is a lot of overhead. HBase-1.1 is
> > rolling
> > > > upgradable and compatible with 1.0, so users should not be stuck with
> > it
> > > > for a long time. it is a matter of overhead of keeping one extra
> branch
> > > and
> > > > release vs whether we would want to support Hbase-1.0 users for 4.5+.
> > > Just
> > > > my 2 cents.
> > > >
> > > > Enis
> > > >
> > > > On Thu, May 21, 2015 at 5:39 PM, rajeshb...@apache.org <
> > > > chrajeshbab...@gmail.com> wrote:
> > > >
> > > >> Makes sense Nick. Cut the new branch from 4.4.0-HBase-1.0 tag.
> > > >>
> > > >> Thanks,
> > > >> Rajeshbabu.
> > > >>
> > > >> On Fri, May 22, 2015 at 5:58 AM, Nick Dimiduk 
> > > wrote:
> > > >>
> > > >> > This looks good except for (1) branch should be cut from the
> > > >> > 4.4.0-HBase-1.0 tag. That way 4.4.0 will be feature-identical
> across
> > > all
> > > >> > releases. Then we'll need to go back over what's landed on
> > > 4.x-HBase-1.0
> > > >> > since 4.4.0 was rel

[VOTE] Release of Apache Phoenix 4.4.0-HBase-1.1 RC0

[rajeshb...@apache.org]

Hi Everyone,

This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.1 RC0. This is the
next minor release of Phoenix 4, compatible with the Apache HBase 1.1.x
branch. The release includes both a source-only release and a convenience
binary release.

The 4.4.0-HBase-1.1 release has feature parity with our latest release
4.4.0-HBase-1.0 release.

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/bin/

Release artifacts are signed with the following key:
http://people.apache.org/~rajeshbabu/E3A65DBC.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=ada3253aadd78380cb279d4f87485388526f1c41
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.1-rc0


For a complete list of changes, see:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin


Vote will be open till 27th May 2015. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

Re: I will make rc tonight IST(I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well)

[rajeshb...@apache.org]

You are correct Anoop. We need to clean the HBase 1.1.0 jars from local
repository. Then we may not see this problem because the fresh jars will be
downloaded from actual repo.

Thanks,
Rajeshbabu.

On Mon, May 25, 2015 at 11:50 AM, Anoop John  wrote:

> This issue is not there in 1.1.0.. It might be some jar improper verison
> issue?
>
> org/apache/hadoop/hbase/NoTagsKeyValue
> at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.
> formNoTagsKeyValue(HFileReaderV2.java:755)
> at org.apache.hadoop.hbase.io.hfile.HFileReaderV3$ScannerV3.
> getKeyValue(HFileReaderV3.java:206)
> at org.apache.hadoop.hbase.regionserver.StoreFileScanner.
> seek(StoreFileScanner.java:161)
> at org.apache.hadoop.hbase.regionserver.StoreFileScanner.
> backwardSeek(StoreFileScanner.java:478)
> As per this trace itself, it is not 1.1.0  hbase-server.jar.  But the
> common jar may be 1.1.0 only and that is why not able to see the new
> class..
>
> -Anoop-
>
> On Sun, May 24, 2015 at 10:18 PM, Ted Yu  wrote:
>
> > Looking at
> >
> >
> https://builds.apache.org/view/All/job/Phoenix-4.4-HBase-1.1/2/testReport/org.apache.phoenix.end2end/GroupByCaseIT/org_apache_phoenix_end2end_GroupByCaseIT/
> > :
> >
> > Caused by: org.apache.hadoop.hbase.DoNotRetryIOException:
> > org.apache.hadoop.hbase.DoNotRetryIOException:
> > java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/NoTagsKeyValue
> > at
> org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2151)
> > at
> org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:101)
> > at
> >
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130)
> > at
> > org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107)
> > at java.lang.Thread.run(Thread.java:724)
> > Caused by: java.lang.NoClassDefFoundError:
> > org/apache/hadoop/hbase/NoTagsKeyValue
> > at
> >
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.formNoTagsKeyValue(HFileReaderV2.java:755)
> > at
> >
> org.apache.hadoop.hbase.io.hfile.HFileReaderV3$ScannerV3.getKeyValue(HFileReaderV3.java:206)
> > at
> >
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:161)
> > at
> >
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.backwardSeek(StoreFileScanner.java:478)
> >
> >
> > NoTagsKeyValue was introduced by:
> >
> >   HBASE-13579 - Avoid isCellTTLExpired() for NO-TAG cases (Ram)
> >
> > which was marked for 1.1.1
> >
> >
> > FYI
> >
> >
> > On Sun, May 24, 2015 at 7:04 AM, rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> > > Hi Ted,
> > >
> > > Tests are failing for both the branches and master branch as well.
> > >
> > > Thanks,
> > > Rajeshbabu.
> > > On May 24, 2015 7:21 PM, "Ted Yu"  wrote:
> > >
> > > > Did the test fail on branch 4.4-HBase-1.1, branch 4.x-HBase-1.1 or
> > both ?
> > > >
> > > > Cheers
> > > >
> > > > On Sun, May 24, 2015 at 2:38 AM, rajeshb...@apache.org <
> > > > chrajeshbab...@gmail.com> wrote:
> > > >
> > > > > I ran the tests multiple times locally and they are always passing.
> > > > >
> > > > > [INFO] --- maven-site-plugin:3.2:attach-descriptor
> > (attach-descriptor)
> > > @
> > > > > phoenix-assembly ---
> > > > > [INFO]
> > > > >
> > >
> 
> > > > > [INFO] Reactor Summary:
> > > > > [INFO]
> > > > > [INFO] Apache Phoenix .
> SUCCESS [
> > > > >  1.531 s]
> > > > > [INFO] Phoenix Core ... SUCCESS
> > > > [49:22
> > > > > min]
> > > > > [INFO] Phoenix - Flume  SUCCESS
> > > > [01:09
> > > > > min]
> > > > > [INFO] Phoenix - Pig .. SUCCESS
> > > > [03:04
> > > > > min]
> > > > > [INFO] Phoenix Query Server Client 
> SUCCESS [
> > > > >  0.469 s]
> > > > > [INFO] Phoenix Query Server ... SUCCESS
> > > > [01:47
> > > > > min]
> > > > > [INFO] Phoenix - P

Re: I will make rc tonight IST(I feel It's correct time to release 4.4.0 with HBase 1.1.0 as well)

[rajeshb...@apache.org]

bq. Anyway, I have added rm -rf ~/.m2/repository/org/apache/hbase at the
beginning of the job.It is downloading the bits from repository.apache.org
correctly it seems.
I have changed the same for other builds and now all the builds are green.
Thanks Enis for the help.

The changes I have done as part of PHOENIX-2008 is the cause of master not
to initialize for more than 3 minutes. So I reverted the patch which is not
required at all.

I have changed 4.x-HBase-1.1 branch version to 4.5-HBase-1.1-SNAPSHOT.
will change 4.4-HBase-1.1 version to 4.4.1-HBASE-SNAPSHOT after release.

Thanks,
Rajeshbabu.

On Wed, May 27, 2015 at 9:08 AM, Enis Söztutar  wrote:

> Rajesh,
>
> I added dependency:tree in jenkins, but that did not reveal anything
> strange:
> https://builds.apache.org/view/All/job/Phoenix-4.4-HBase-1.1/3/console
>
> The HBASE-13579 not being in 1.1.0 means that maybe how a 1.1.1-SNAPSHOT
> got installed as 1.1.0?
>
> Anyway, I have added rm -rf ~/.m2/repository/org/apache/hbase at the
> beginning of the job. It is downloading the bits from
> repository.apache.org
> correctly it seems. Lets watch the build:
> https://builds.apache.org/view/All/job/Phoenix-4.4-HBase-1.1/4/console
>
> Not directly related, but you should also update the version strings in
> 4.4-HBase-1.1 and 4.x-HBase-1.1 branches. Right now they do not have the
> -HBase-1.1 suffix.
>
> Enis
>
> On Mon, May 25, 2015 at 2:10 AM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > You are correct Anoop. We need to clean the HBase 1.1.0 jars from local
> > repository. Then we may not see this problem because the fresh jars will
> be
> > downloaded from actual repo.
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Mon, May 25, 2015 at 11:50 AM, Anoop John 
> > wrote:
> >
> > > This issue is not there in 1.1.0.. It might be some jar improper
> verison
> > > issue?
> > >
> > > org/apache/hadoop/hbase/NoTagsKeyValue
> > > at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.
> > > formNoTagsKeyValue(HFileReaderV2.java:755)
> > > at org.apache.hadoop.hbase.io.hfile.HFileReaderV3$ScannerV3.
> > > getKeyValue(HFileReaderV3.java:206)
> > > at org.apache.hadoop.hbase.regionserver.StoreFileScanner.
> > > seek(StoreFileScanner.java:161)
> > > at org.apache.hadoop.hbase.regionserver.StoreFileScanner.
> > > backwardSeek(StoreFileScanner.java:478)
> > > As per this trace itself, it is not 1.1.0  hbase-server.jar.  But the
> > > common jar may be 1.1.0 only and that is why not able to see the new
> > > class..
> > >
> > > -Anoop-
> > >
> > > On Sun, May 24, 2015 at 10:18 PM, Ted Yu  wrote:
> > >
> > > > Looking at
> > > >
> > > >
> > >
> >
> https://builds.apache.org/view/All/job/Phoenix-4.4-HBase-1.1/2/testReport/org.apache.phoenix.end2end/GroupByCaseIT/org_apache_phoenix_end2end_GroupByCaseIT/
> > > > :
> > > >
> > > > Caused by: org.apache.hadoop.hbase.DoNotRetryIOException:
> > > > org.apache.hadoop.hbase.DoNotRetryIOException:
> > > > java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/NoTagsKeyValue
> > > > at
> > > org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2151)
> > > > at
> > > org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:101)
> > > > at
> > > >
> > >
> >
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130)
> > > > at
> > > > org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107)
> > > > at java.lang.Thread.run(Thread.java:724)
> > > > Caused by: java.lang.NoClassDefFoundError:
> > > > org/apache/hadoop/hbase/NoTagsKeyValue
> > > > at
> > > >
> > >
> >
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.formNoTagsKeyValue(HFileReaderV2.java:755)
> > > > at
> > > >
> > >
> >
> org.apache.hadoop.hbase.io.hfile.HFileReaderV3$ScannerV3.getKeyValue(HFileReaderV3.java:206)
> > > > at
> > > >
> > >
> >
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:161)
> > > > at
> > > >
> > >
> >
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.backwardSeek(StoreFileScanner.java:478)
> > > >
> > > >
> > > > NoTagsKeyValue was introduced by:
> > > >

Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.1 RC0

[rajeshb...@apache.org]

+1.

- verified signing key for src and bin tgzs
- extracted src tgz and ran full integration tests and it passed.
- ran apache-rat check no issues reported.
- installed HBase 1.1.0 in standalone mode and ran examples and no issues.
- checked compatibility with older version clients. Every things looks fine.
- Ran some performance tests with performance.py and compared performance
numbers between this RC and 4.4.0-HBase-0.98 release. The number looks
mostly same.
- loaded some data and created indexes and things are fine.
- tested UDFs and things are fine.
- started query server and ran some queries from sqlline-thin command line.
They are fine.
- enabled tracing and ran some queries and checked the trace information
for the queries. It's fine.

Thanks,
Rajeshbabu.

On Mon, May 25, 2015 at 8:23 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Hi Everyone,
>
> This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.1 RC0. This is
> the
> next minor release of Phoenix 4, compatible with the Apache HBase 1.1.x
> branch. The release includes both a source-only release and a convenience
> binary release.
>
> The 4.4.0-HBase-1.1 release has feature parity with our latest release
> 4.4.0-HBase-1.0 release.
>
> The source tarball, including signatures, digests, etc can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/src/
>
> The binary artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/bin/
>
> Release artifacts are signed with the following key:
> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/phoenix/KEYS
>
> The hash and tag to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=ada3253aadd78380cb279d4f87485388526f1c41
>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.1-rc0
>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> For a complete list of changes, see:
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
>
>
> <https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a>
> Vote will be open till 27th May 2015. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team
>

[RESULT][VOTE] Release of Apache Phoenix 4.4.0-HBase-1.1 RC0

[rajeshb...@apache.org]

Vote is closed now. The vote has passed with 3 binding +1 votes and no 0's
or -1's. I will publish the release artifacts shortly. Thanks everyone for
helping with the release!

Thanks,
Rajeshbabu.

-- Forwarded message --
From: Nick Dimiduk 
Date: Fri, May 29, 2015 at 2:47 AM
Subject: Re: [VOTE] Release of Apache Phoenix 4.4.0-HBase-1.1 RC0
To: phoenix-dev 


+1 approve.

- verified signing key for both tgzs
- run with 1.1.0.1 and checkout of branch-1.1/a1043fb in local mode
- create table, load example data with psql, list tables and content
- start query server and perform similar experiments there; everything
works as expected and log levels look good
- checked src tgzl with apache-rat:check, and verified no .class, .jar,
.orig, ~ files present
- build src tgz, UT all pass (with PHOENIX-1963 applied, as before)


On Sun, May 24, 2015 at 7:53 PM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> Hi Everyone,
>
> This is a call for a vote on Apache Phoenix 4.4.0-HBase-1.1 RC0. This is
> the
> next minor release of Phoenix 4, compatible with the Apache HBase 1.1.x
> branch. The release includes both a source-only release and a convenience
> binary release.
>
> The 4.4.0-HBase-1.1 release has feature parity with our latest release
> 4.4.0-HBase-1.0 release.
>
> The source tarball, including signatures, digests, etc can be found at:
>
>
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/src/
>
> The binary artifacts can be found at:
>
>
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.4.0-HBase-1.1-rc0/bin/
>
> Release artifacts are signed with the following key:
> http://people.apache.org/~rajeshbabu/E3A65DBC.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/phoenix/KEYS
>
> The hash and tag to be voted upon:
>
>
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=ada3253aadd78380cb279d4f87485388526f1c41
>
>
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.4.0-HBase-1.1-rc0
>
> <
>
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> >
> For a complete list of changes, see:
> <
>
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> >
>
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329581&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8a452be5f2e3253400f2c8b56c26613facdafc2b%7Clin
>
> <
>
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a436a21140ceaf97d08eebaaf5c2fcda3bd45e0a
> >
> Vote will be open till 27th May 2015. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team
>

[ANNOUNCE] Apache Phoenix 4.4-0-HBase-1.1 released

[rajeshb...@apache.org]

The Apache Phoenix team is pleased to announce the immediate
availability of the 4.4.0-HBase-1.1 release compatible with HBase 1.1.x.

The 4.4.0-HBase-1.1 release has feature parity with our 4.4.0-HBase-1.0
release.

The release is available through maven or may be downloaded here[1].

Thanks to all the contributors who made this release possible!

Regards,
The Apache Phoenix Team

[1] http://phoenix.apache.org/download.html

Re: [ANNOUNCE] Apache Phoenix 4.4-0-HBase-0.98 released

[rajeshb...@apache.org]

@Josh
I am pushing the jars to maven. Will ping you once done.
Thanks,
Rajeshbabu.

On Tue, Jun 2, 2015 at 7:25 PM, Josh Mahonin  wrote:

> Out of curiosity, did this release make it up to Maven central? Or am I
> missing a repository? I can't find published JARs anywhere.
>
> http://mvnrepository.com/artifact/org.apache.phoenix/phoenix
>
> https://repository.apache.org/content/repositories/releases/org/apache/phoenix/phoenix-core/
>
>
> On Thu, May 21, 2015 at 9:15 PM, rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > The Apache Phoenix team is pleased to announce the immediate
> > availability of the 4.4.0-HBase-0.98 release compatible with HBase 0.98.x
> > .
> > Highlights include:
> >
> > - spark integration[1]
> > - query server[2]
> > - support for user defined functions[3]
> > - pherf - load tester measures throughput[4]
> > - support union All and union queries in subquery[5].
> > - 7.5x performance improvement for non aggregate, unordered queries
> > - many math and date/time buit-in functions
> > - mr job to populate indexes
> > - improvements in tracing and monitoring.
> > - some more improvements in CBO
> > - over 70 bug fixes and etc...
> >
> > The release is available through maven or may be downloaded here [6].
> >
> > Thanks to all the contributors who made this release possible!
> >
> > Regards,
> > The Apache Phoenix Team
> >
> > [1] http://phoenix.apache.org/phoenix_spark.html
> > [2] http://phoenix.apache.org/server.html
> > [3] http://phoenix.apache.org/udf.html
> > [4] http://phoenix.apache.org/pherf.html
> > [5] http://phoenix.apache.org/language/index.html#select
> > [6] http://phoenix.apache.org/download.html
> >
>

Re: [ANNOUNCE] Apache Phoenix 4.4-0-HBase-0.98 released

[rajeshb...@apache.org]

Here you can find the jars in maven repo.

https://repository.apache.org/content/repositories/releases/org/apache/phoenix/


Thanks,
Rajeshbabu.

On Wed, Jun 3, 2015 at 10:53 AM, rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:

> @Josh
> I am pushing the jars to maven. Will ping you once done.
> Thanks,
> Rajeshbabu.
>
> On Tue, Jun 2, 2015 at 7:25 PM, Josh Mahonin 
> wrote:
>
>> Out of curiosity, did this release make it up to Maven central? Or am I
>> missing a repository? I can't find published JARs anywhere.
>>
>> http://mvnrepository.com/artifact/org.apache.phoenix/phoenix
>>
>> https://repository.apache.org/content/repositories/releases/org/apache/phoenix/phoenix-core/
>>
>>
>> On Thu, May 21, 2015 at 9:15 PM, rajeshb...@apache.org <
>> chrajeshbab...@gmail.com> wrote:
>>
>> > The Apache Phoenix team is pleased to announce the immediate
>> > availability of the 4.4.0-HBase-0.98 release compatible with HBase
>> 0.98.x
>> > .
>> > Highlights include:
>> >
>> > - spark integration[1]
>> > - query server[2]
>> > - support for user defined functions[3]
>> > - pherf - load tester measures throughput[4]
>> > - support union All and union queries in subquery[5].
>> > - 7.5x performance improvement for non aggregate, unordered queries
>> > - many math and date/time buit-in functions
>> > - mr job to populate indexes
>> > - improvements in tracing and monitoring.
>> > - some more improvements in CBO
>> > - over 70 bug fixes and etc...
>> >
>> > The release is available through maven or may be downloaded here [6].
>> >
>> > Thanks to all the contributors who made this release possible!
>> >
>> > Regards,
>> > The Apache Phoenix Team
>> >
>> > [1] http://phoenix.apache.org/phoenix_spark.html
>> > [2] http://phoenix.apache.org/server.html
>> > [3] http://phoenix.apache.org/udf.html
>> > [4] http://phoenix.apache.org/pherf.html
>> > [5] http://phoenix.apache.org/language/index.html#select
>> > [6] http://phoenix.apache.org/download.html
>> >
>>
>
>

Re: [DISCUSS] drop 4.x-HBase-1.1 branch

[rajeshb...@apache.org]

+1 to drop.

On Wed, Jun 17, 2015 at 3:08 AM, James Taylor 
wrote:

> Until master would diverge from 4.x-HBase-1.1 branch, I don't think we
> need it, so I propose we drop it. It's just added overhead at this
> point and is missing commits from master as well.
>
> Please let me know if you think we need to keep it around.
>
> Thanks,
> James
>

Re: [ANNOUNCE] Josh Mahonin added as Apache Phoenix committer

[rajeshb...@apache.org]

Congratulations and Welcome, Josh!

Thanks,
Rajeshbabu.

On Wed, Jun 24, 2015 at 5:38 AM, Eli Levine  wrote:

> Welcome, Josh!
>
> On Tue, Jun 23, 2015 at 1:03 PM, Thomas D'Silva 
> wrote:
>
> > Welcome Josh!
> >
> > On Tue, Jun 23, 2015 at 10:24 AM, Samarth Jain 
> wrote:
> > > Congratulations and welcome, Josh.
> > > On Tuesday, June 23, 2015, Gabriel Reid 
> wrote:
> > >
> > >> Congrats and welcome Josh!
> > >>
> > >>
> > >> On Tue, Jun 23, 2015 at 7:10 PM Jesse Yates  > >> > wrote:
> > >>
> > >> > Congrats and welcome!
> > >> >
> > >> > On Tue, Jun 23, 2015, 10:01 AM Ravi Kiran <
> maghamraviki...@gmail.com
> > >> >
> > >> > wrote:
> > >> >
> > >> > > Welcome Josh!!
> > >> > >
> > >> > > On Tue, Jun 23, 2015 at 11:55 AM, Nick Dimiduk <
> ndimi...@apache.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > Nice work, congratulations Josh, and welcome!
> > >> > > >
> > >> > > > On Tue, Jun 23, 2015 at 9:40 AM, James Taylor <
> > >> jamestay...@apache.org >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > On behalf of the Apache Phoenix PMC, I'm pleased to announce
> > that
> > >> > Josh
> > >> > > > > Mahonin has accepted our invitation to become a committer on
> the
> > >> > > > > Apache Phoenix project. He's been the force behind our
> > >> Phoenix-Spark
> > >> > > > > integration[1] and has done an excellent job moving it
> forward.
> > >> > > > >
> > >> > > > > Great job, Josh. Welcome aboard. Looking forward to many more
> > >> > > > > contributions!
> > >> > > > >
> > >> > > > > Regards,
> > >> > > > > James
> > >> > > > >
> > >> > > > > [1] https://phoenix.apache.org/phoenix_spark.html
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
>

Re: [VOTE] Release of Apache Phoenix 4.5.0-HBase-1.1 RC0

[rajeshb...@apache.org]

+1
- verified signatures,
- ran full integration test suite, all tests passed.
- installed HBase 1.1 cluster with the RC and ran examples queries,
performance script with 1 million records. Everything fine.

Thanks,
Rajeshbabu.

On Sun, Jul 26, 2015 at 2:14 AM, Gabriel Reid 
wrote:

> +1 to release.
>
> Verified signatures, ran full integration test suite, verified contents of
> git tag vs contents of source distribution.
>
> - Gabriel
>
> On Thu, Jul 23, 2015 at 7:20 AM James Taylor 
> wrote:
>
> > Hi Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.5.0-HBase-1.1 RC0. This is
> > the next minor release of Phoenix 4, compatible with the 1.1 branch of
> > Apache HBase. The release includes both a source-only release and a
> > convenience binary release.
> >
> > This release has feature parity with our pending 4.5.0-HBase-0.98 release
> > and includes the following improvements:
> > - Support for adding columns to tables with views
> > - Collection of per statement client-side metrics
> > - Ability to issue SELECT without FROM clause
> > - Pherf support for mixed read/write workloads
> > - Many new math and ARRAY built-in functions
> > - Manage UDF jars through SQL commands
> > - Improvements to MR index build
> >
> > The source tarball, including signatures, digests, etc can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-1.1-rc0/src/
> >
> > The binary artifacts can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-1.1-rc0/bin/
> >
> > For a complete list of changes, see:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=12332152
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=b7cd7e505ed14338d9bcd6f49f659e7f067de0d8
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.0-HBase-1.1-rc0
> >
> > Vote will be open for at least 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
>

Re: [VOTE] Release of Apache Phoenix 4.5.0-HBase-1.0 RC0

[rajeshb...@apache.org]

I am also seeing the same failures with Join related tests.
I  often the see the failures, But they are passing when I run individually.

testJoinWithSubquery[2](org.apache.phoenix.end2end.SpooledSortMergeJoinIT)
Time elapsed: 0.134 sec  <<< ERROR!

org.apache.phoenix.exception.PhoenixIOException:
org.apache.hadoop.hbase.DoNotRetryIOException: Join.CustomerTable:
java.lang.OutOfMemoryError: unable to create new native thread

testJoinWithSubquery[2](org.apache.phoenix.end2end.SortMergeJoinIT)  Time
elapsed: 0.069 sec  <<< ERROR!

org.apache.phoenix.exception.PhoenixIOException:
org.apache.hadoop.hbase.DoNotRetryIOException: Join.CustomerTable: unable
to create new native thread



On Sun, Jul 26, 2015 at 2:18 AM, Gabriel Reid 
wrote:

> I'm having problems running the full test suite. I'm getting the following
> error while running "mvn clean install":
>
> testInnerJoin[2](org.apache.phoenix.end2end.SpooledSortMergeJoinIT)  Time
> elapsed: 0.229 sec  <<< ERROR!
> org.apache.phoenix.exception.PhoenixIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException: Join.ItemTable:
> java.lang.OutOfMemoryError: unable to create new native thread
>
> I don't get anything like this on the HBase 1.1 and HBase 0.98 versions. Is
> anyone else seeing anything like this?
>
> - Gabriel
>
>
>
> On Sat, Jul 25, 2015 at 2:41 AM Mujtaba Chohan  wrote:
>
> > +1 on release.
> >
> > Verified tests and licenses.
> >
> > On Wednesday, July 22, 2015, James Taylor 
> wrote:
> >
> > > Hi Everyone,
> > >
> > > This is a call for a vote on Apache Phoenix 4.5.0-HBase-1.0 RC0. This
> is
> > > the next minor release of Phoenix 4, compatible with the 1.0 branch of
> > > Apache HBase. The release includes both a source-only release and a
> > > convenience binary release.
> > >
> > > This release has feature parity with our pending 4.5.0-HBase-0.98
> release
> > > and includes the following improvements:
> > > - Support for adding columns to tables with views
> > > - Collection of per statement client-side metrics
> > > - Ability to issue SELECT without FROM clause
> > > - Pherf support for mixed read/write workloads
> > > - Many new math and ARRAY built-in functions
> > > - Manage UDF jars through SQL commands
> > > - Improvements to MR index build
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-1.0-rc0/src/
> > >
> > > The binary artifacts can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-1.0-rc0/bin/
> > >
> > > For a complete list of changes, see:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=12332152
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/mujtaba.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=083998f15d306e6a4f8535cc3850e6edba9526f8
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.0-HBase-1.0-rc0
> > >
> > > Vote will be open for at least 72 hours. Please vote:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > The Apache Phoenix Team
> > >
> >
>

Re: [VOTE] Release of Apache Phoenix 4.5.0-HBase-0.98 RC0

[rajeshb...@apache.org]

+1
- Verified signatures
- Ran full integration tests and all are passed.
- Installed 0.98 cluster with the RC and ran the examples. Everything fine.

Thanks,
Rajeshbabu.


On Mon, Jul 27, 2015 at 8:38 AM, Jan Fernando 
wrote:

> +1 Ran various internal regression test suites and no issues found.
>
> On Wed, Jul 22, 2015 at 5:28 PM, James Taylor 
> wrote:
>
> > Hi Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.5.0-HBase-0.98 RC0. This is
> > the
> > next minor release of Phoenix 4, compatible with the 0.98 branch of
> > Apache HBase. The release includes both a source-only release and a
> > convenience binary release.
> >
> > Improvements include:
> > - Support for adding columns to tables with views
> > - Collection of per statement client-side metrics
> > - Ability to issue SELECT without FROM clause
> > - Pherf support for mixed read/write workloads
> > - Many new math and ARRAY built-in functions
> > - Manage UDF jars through SQL commands
> > - Improvements to MR index build
> >
> > The source tarball, including signatures, digests, etc can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-0.98-rc0/src/
> >
> > The binary artifacts can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.0-HBase-0.98-rc0/bin/
> >
> > For a complete list of changes, see:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=12332152
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=26ba0159e08aad05e10e921209a65082fdb7d954
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.0-HBase-0.98-rc0
> >
> > Vote will be open for at least 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
>