willshen, I think bugfix PHOENIX-5217 could be inclueded.
At 2019-04-17 01:28:43, "William Shen" <wills...@marinsoftware.com> wrote:
>Bump, anyone else would like to chime in regarding what should or should
>not be included as part of 4.14.2?
>
>Right now we have, based on the filter:
>Issue Type Issue key Summary Status Resolution
>Bug PHOENIX-5243 PhoenixResultSet#next() closes the result set if scanner
>returns null Patch Available
>Bug PHOENIX-5207 Create index if not exists fails incorrectly if table has
>'maxIndexesPerTable' indexes already Resolved Fixed
>Bug PHOENIX-5184 HBase and Phoenix connection leaks in Indexing code path,
>OrphanViewTool and PhoenixConfigurationUtil Resolved Fixed
>Bug PHOENIX-5169 Query logger is still initialized for each query when the
>log level is off Resolved Fixed
>Improvement PHOENIX-5131 Make spilling to disk for order/group by
>configurable Resolved Fixed
>Bug PHOENIX-5126 RegionScanner leak leading to store files not getting
>cleared Resolved Fixed
>Bug PHOENIX-5123 Avoid using MappedByteBuffers for server side GROUP BY
>Resolved Fixed
>Bug PHOENIX-5122 PHOENIX-4322 breaks client backward compatibility Resolved
>Fixed
>Bug PHOENIX-5101 ScanningResultIterator getScanMetrics throws NPE Resolved
>Fixed
>Bug PHOENIX-5084 Changes from Transactional Tables are not visible to query
>in different client Resolved Fixed
>Bug PHOENIX-5073 Invalid PIndexState during rolling upgrade from 4.13 to
>4.14 Resolved Fixed
>Improvement PHOENIX-5069 Use asynchronous refresh to provide non-blocking
>Phoenix Stats Client Cache Resolved Fixed
>Improvement PHOENIX-5026 Add client setting to disable server side mutations
>Resolved Fixed
>Improvement PHOENIX-4900 Modify MAX_MUTATION_SIZE_EXCEEDED and
>MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning
>autocommit on for deletes Resolved Fixed
>
>On Sat, Apr 13, 2019 at 5:59 PM William Shen <wills...@marinsoftware.com>
>wrote:
>
>> Also, there're a handful of tickets already marked with Fix Version 4.14.2:
>>
>> https://issues.apache.org/jira/browse/PHOENIX-5207?jql=project%20%3D%20PHOENIX%20AND%20fixVersion%20%3D%204.14.2
>>
>> On Fri, Apr 12, 2019 at 3:09 PM Chinmay Kulkarni <
>> chinmayskulka...@gmail.com> wrote:
>>
>>> +1 to the idea of a 4.14.2 release. Here are some JIRAs to backport that
>>> come to mind:
>>>
>>> https://issues.apache.org/jira/browse/PHOENIX-5184
>>> https://issues.apache.org/jira/browse/PHOENIX-5169
>>> https://issues.apache.org/jira/browse/PHOENIX-5131
>>>
>>> Thanks,
>>> Chinmay
>>>
>>>
>>> On Fri, Apr 12, 2019 at 1:33 PM William Shen <wills...@marinsoftware.com>
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > Since there're still some blockers for 4.15, what does the community
>>> feel
>>> > about back-porting some of the bug fixes for a 4.14.2 release?
>>> >
>>> > One issue I have in mind is the NPE fix (
>>> > https://issues.apache.org/jira/browse/PHOENIX-5101). Is there anything
>>> > else
>>> > that would be of interest?
>>> >
>>> > Thanks
>>> >
>>> > - Will
>>> >
>>>
>>>
>>> --
>>> Chinmay Kulkarni
>>> M.S. Computer Science,
>>> University of Illinois at Urbana-Champaign.
>>> B. Tech Computer Engineering,
>>> College of Engineering, Pune.
>>>
>>
