Thanks James and Samarth for suggestions. Sure I can take the issues from
4.5.0 and few things found after that.

I will try to make the RC on Friday.

Thanks,
Rajeshbabu.



On Mon, Aug 24, 2015 at 11:00 PM, Samarth Jain <[email protected]> wrote:

> +1 to just taking the latest from 4.5 branches. In your list, there are a
> few bug fixes that include follow up work to new features that were added
> in 4.5.
>
> For ex -
>
> [PHOENIX-2111 <https://issues.apache.org/jira/browse/PHOENIX-2111>] -
> Race condition on creation of new view and adding of column to base table
>
> [PHOENIX-2057 <https://issues.apache.org/jira/browse/PHOENIX-2057>] -
> Acquire lock in MetaDataEndPointImpl.addRowsToChildViews() before calling
> doGetTable()
>
> The above two are follow up work to
> https://issues.apache.org/jira/browse/PHOENIX-1504. PHOENIX-1504 has
> un-compatible changes that violates the backward and forward compatibility
> contract we have for our patch releases.
>
> On Mon, Aug 24, 2015 at 10:20 AM, James Taylor <[email protected]>
> wrote:
>
> > Good list. I'd recommend including PHOENIX-2177, PHOENIX-2138, and
> > PHOENIX-2149 too. One more that's not fixed yet, but to keep an eye on is
> > PHOENIX-2195.
> >
> > You might consider just going to the latest on 4.5 branches. Is there
> > really anything you *don't* want?
> >
> > Thanks,
> > James
> >
> > On Mon, Aug 24, 2015 at 9:23 AM, [email protected] <
> > [email protected]> wrote:
> >
> > > Hi James,
> > > Here is the list of issues going be backport and some more new recent
> > bugs.
> > >
> > >    - PHOENIX-1659 <https://issues.apache.org/jira/browse/PHOENIX-1659
> >]
> > -
> > >    PhoenixDatabaseMetaData.getColumns does not return REMARKS column
> > >
> > >    - [PHOENIX-2030 <https://issues.apache.org/jira/browse/PHOENIX-2030
> >]
> > -
> > >    CsvBulkLoadTool should use logical name of the table for output
> > > directory
> > >    suffix
> > >    - [PHOENIX-2063 <https://issues.apache.org/jira/browse/PHOENIX-2063
> >]
> > -
> > >    Row value constructor doesn't work when used in COUNT DISTINCT
> > >    - [PHOENIX-2067 <https://issues.apache.org/jira/browse/PHOENIX-2067
> >]
> > -
> > >    Sort order incorrect for variable length DESC columns
> > >    - [PHOENIX-2074 <https://issues.apache.org/jira/browse/PHOENIX-2074
> >]
> > -
> > >    StackOverflowError with RoundRobinResultIterator
> > >    - [PHOENIX-2125 <https://issues.apache.org/jira/browse/PHOENIX-2125
> >]
> > -
> > >    ORDER BY on full PK on salted table does not work
> > >    - [PHOENIX-2131 <https://issues.apache.org/jira/browse/PHOENIX-2131
> >]
> > -
> > >    CastParseNode.toSQL omits closing parenthesis
> > >    - [PHOENIX-2120 <https://issues.apache.org/jira/browse/PHOENIX-2120
> >]
> > -
> > >    Padding character is not inverted as required for DESC CHAR columns
> > >    - [PHOENIX-1978 <https://issues.apache.org/jira/browse/PHOENIX-1978
> >]
> > -
> > >    UDF ArgumentTypeMismatchException
> > >
> > >
> > >
> > >    - [PHOENIX-1277 <https://issues.apache.org/jira/browse/PHOENIX-1277
> >]
> > -
> > >    CSVCommonsLoader not allowing null CHAR values (non PK)
> > >    - [PHOENIX-1827 <https://issues.apache.org/jira/browse/PHOENIX-1827
> >]
> > -
> > >    TrackOrderPreservingExpressionCompiler may falsely say ORDER BY is
> > order
> > >    preserving
> > >    - [PHOENIX-2014 <https://issues.apache.org/jira/browse/PHOENIX-2014
> >]
> > -
> > >    WHERE search condition ignored when also using row value constructor
> > in
> > > view
> > >    - [PHOENIX-2022 <https://issues.apache.org/jira/browse/PHOENIX-2022
> >]
> > -
> > >    BaseRegionScanner.next should be abstract
> > >    - [PHOENIX-2029 <https://issues.apache.org/jira/browse/PHOENIX-2029
> >]
> > -
> > >    Queries are making two rpc calls for getTable
> > >    - [PHOENIX-2040 <https://issues.apache.org/jira/browse/PHOENIX-2040
> >]
> > -
> > >    Mark spark/scala dependencies as 'provided’
> > >    - [PHOENIX-2050 <https://issues.apache.org/jira/browse/PHOENIX-2050
> >]
> > -
> > >    Avoid checking for child views unless operating on table
> > >    - [PHOENIX-2057 <https://issues.apache.org/jira/browse/PHOENIX-2057
> >]
> > -
> > >    Acquire lock in MetaDataEndPointImpl.addRowsToChildViews() before
> > > calling
> > >    doGetTable()
> > >    - [PHOENIX-2059 <https://issues.apache.org/jira/browse/PHOENIX-2059
> >]
> > -
> > >    MR index build does not handle table with a schema name correctly
> > >    - [PHOENIX-2065 <https://issues.apache.org/jira/browse/PHOENIX-2065
> >]
> > -
> > >    Throw TableNotFoundException when select all columns of one column
> > > family
> > >    from the table with schema
> > >    - [PHOENIX-2073 <https://issues.apache.org/jira/browse/PHOENIX-2073
> >]
> > -
> > >    Two bytes character in LIKE expression is not allowed
> > >    - [PHOENIX-2075 <https://issues.apache.org/jira/browse/PHOENIX-2075
> >]
> > -
> > >    MR integration uses single mapper unless table is salted
> > >    - [PHOENIX-2096 <https://issues.apache.org/jira/browse/PHOENIX-2096
> >]
> > -
> > >    Tweak criteria for when round robin iterator is used
> > >    - [PHOENIX-2111 <https://issues.apache.org/jira/browse/PHOENIX-2111
> >]
> > -
> > >    Race condition on creation of new view and adding of column to base
> > > table
> > >    - [PHOENIX-2112 <https://issues.apache.org/jira/browse/PHOENIX-2112
> >]
> > -
> > >    Phoenix-Spark need to support UTF8String for spark 1.4.0
> > >    - [PHOENIX-2139 <https://issues.apache.org/jira/browse/PHOENIX-2139
> >]
> > -
> > >    LIKE '%' is not filtering out null columns
> > >    - [PHOENIX-2137] - Range query on DECIMAL DESC sometimes incorrect
> > >    - [PHOENIX-2171] - DOUBLE and FLOAT DESC are stored as ASC
> > >
> > >
> > >
> > >
> > > On Mon, Aug 24, 2015 at 9:33 PM, James Taylor <[email protected]>
> > > wrote:
> > >
> > > > +1. Thanks, Rajeshbabu. Do you have a list of the issues you're
> > planning
> > > to
> > > > back port?
> > > >
> > > > On Mon, Aug 24, 2015 at 8:58 AM, [email protected] <
> > > > [email protected]> wrote:
> > > >
> > > > > Hi Team,
> > > > >
> > > > > We have fixed around 20 major issues after 4.4.0. Some of them are
> > > > > committed to 4.4.1. I am planning to make the 4.4.1 RC by porting
> > > > remaining
> > > > > bug fixes.
> > > > >
> > > > > What do you say?
> > > > >
> > > > > Thanks,
> > > > > Rajeshbabu.
> > > > >
> > > >
> > >
> >
>

Reply via email to