phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 1emo <...@git.apache.org>
Subject [GitHub] phoenix pull request #237: 4.9 h base 1.2
Date Fri, 24 Mar 2017 09:34:28 GMT
GitHub user 1emo opened a pull request:

    https://github.com/apache/phoenix/pull/237

    4.9 h base 1.2

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/phoenix 4.9-HBase-1.2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/237.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #237
    
----
commit 648d2b28b84001251c02dc8d94cd89c82a2a8a69
Author: Mujtaba <mujtaba@apache.org>
Date:   2016-11-23T17:59:51Z

    Set version to 4.9.1-HBase-1.2-SNAPSHOT after release

commit 45f2b1d570f6136df0ec7a9f0028aa485cf58d7d
Author: Thomas D'Silva <tdsilva@salesforce.com>
Date:   2016-12-08T07:59:11Z

    PHOENIX-3522 Altering the mutability of a parent table does not propagate to the child
views

commit 293f6b7a8b457ea96f3973cc144bf9c8d78403aa
Author: Samarth <samarth.jain@salesforce.com>
Date:   2016-12-12T20:00:01Z

    Memory Leak in RenewLeaseTask

commit f65df7c7156cc968f3ca3015b8a0cd2cd4c806e4
Author: Samarth <samarth.jain@salesforce.com>
Date:   2016-12-12T20:00:32Z

    TTL on UPGRADE_LOCK cell causes upgrade to fail

commit 796808fe487b15515e150fa156e8147ff2153a87
Author: Samarth <samarth.jain@salesforce.com>
Date:   2016-12-15T23:40:36Z

    PHOENIX-3537 Clients not able to resolve sequences when the SYSTEM.SEQUENCE table is salted

commit a107c0eedd949cd188493f0c94fa11dee12d501b
Author: Samarth <samarth.jain@salesforce.com>
Date:   2016-12-21T23:09:27Z

    PHOENIX-3535 Fix race condition in ConnectionQueryServicesImpl#acquireUpgradeMutex

commit bd227a7b4d95d6aec1527b664b723d42e2ee7ecc
Author: Samarth <samarth.jain@salesforce.com>
Date:   2016-12-22T01:47:10Z

    PHOENIX-3535 Addendum to fix test failures

commit baf3b7c04ab48b381b90b0cdba753232f72efe58
Author: Thomas D'Silva <tdsilva@salesforce.com>
Date:   2016-12-21T01:56:37Z

    PHOENIX-3516 Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true

commit fb504f2d739e13f2076b8ead234da927ce67e1e5
Author: Thomas D'Silva <tdsilva@salesforce.com>
Date:   2016-12-23T01:29:35Z

    PHOENIX-3516 Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true
(addendum)

commit f34a605a3934cb41bec8e06244992a82fd895b71
Author: Andrew Purtell <apurtell@apache.org>
Date:   2017-01-05T00:48:44Z

    PHOENIX-3563 Ensure we release ZooKeeper resources allocated by the Tephra client embedded
in the Phoenix connection

commit 71a5434b29b1ecb3d9510cfd8f78feefcd1bf2f2
Author: Samarth <samarth.jain@salesforce.com>
Date:   2017-01-11T01:38:46Z

    PHOENIX-3584 Expose metrics for ConnectionQueryServices instances and their allocators
in the JVM

commit a967db5d8508c38bd7808be37093cc1bb898828d
Author: Samarth <samarth.jain@salesforce.com>
Date:   2017-01-26T23:51:11Z

    PHOENIX-3614 Use unique name for index in TransactionIT#testNonTxToTxTable

commit 4855511513ed864b6c6866ce2ca592a412da0c46
Author: Josh Elser <elserj@apache.org>
Date:   2017-02-16T19:47:35Z

    PHOENIX-3684 Handle _HOST in principal specified in JDBC url
    
    When the user provides a principal with the _HOST "magic string"
    in it, Phoenix was incorrectly re-logging that user in. This results
    in an application that creates a new HConnection and ZK connection
    for every Phoenix connection which saturates connections to ZK.

commit bf91232dfd1a4f23dc36cb9629d670f66f34af42
Author: Josh Elser <elserj@apache.org>
Date:   2017-02-27T21:55:42Z

    PHOENIX-3698 No-args constructor for IndexedWALEditCodec
    
    Change-Id: Ic36c61a314e92aa9a8cdf496e210909abe5829dc

commit 0166ffefefe91c9eed59f91101470091126f3220
Author: Ankit Singhal <ankitsinghal59@gmail.com>
Date:   2017-03-06T09:39:41Z

    Higher memory consumption on RS leading to OOM/abort on immutable index creation with
multiple regions on single RS

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message