[
https://issues.apache.org/jira/browse/PHOENIX-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611319#comment-16611319
]
Hudson commented on PHOENIX-4666:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #2032 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/2032/])
PHOENIX-4666 Persistent subquery cache for hash joins (elserj: rev
87cc9b45f959664b0069132ca00878ab9c60ab88)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/iterate/BaseResultIterators.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/join/HashCacheFactory.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/GlobalCache.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/iterate/TableResultIterator.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/HashJoinRegionScanner.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/generated/ServerCachingProtos.java
* (edit) phoenix-protocol/src/main/ServerCachingService.proto
* (edit) phoenix-protocol/src/main/build-proto.sh
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/compile/StatementContext.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/join/HashCacheClient.java
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/cache/TenantCacheTest.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/cache/ServerCacheClient.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/parse/HintNode.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
* (add)
phoenix-core/src/it/java/org/apache/phoenix/end2end/join/HashJoinPersistentCacheIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/TenantCache.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/cache/TenantCacheImpl.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/ServerCachingEndpointImpl.java
> Add a subquery cache that persists beyond the life of a query
> -------------------------------------------------------------
>
> Key: PHOENIX-4666
> URL: https://issues.apache.org/jira/browse/PHOENIX-4666
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Marcell Ortutay
> Assignee: Marcell Ortutay
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 298.patch, 298.patch, 298.patch, 298.patch,
> PHOENIX-4666-subquery-cache-4.x-HBase-1.4.patch,
> PHOENIX-4666-subquery-cache-4.x-HBase-1.4.patch
>
>
> The user list thread for additional context is here:
> [https://lists.apache.org/thread.html/e62a6f5d79bdf7cd238ea79aed8886816d21224d12b0f1fe9b6bb075@%3Cuser.phoenix.apache.org%3E]
> ----
> A Phoenix query may contain expensive subqueries, and moreover those
> expensive subqueries may be used across multiple different queries. While
> whole result caching is possible at the application level, it is not possible
> to cache subresults in the application. This can cause bad performance for
> queries in which the subquery is the most expensive part of the query, and
> the application is powerless to do anything at the query level. It would be
> good if Phoenix provided a way to cache subquery results, as it would provide
> a significant performance gain.
> An illustrative example:
> SELECT * FROM table1 JOIN (SELECT id_1 FROM large_table WHERE x = 10)
> expensive_result ON table1.id_1 = expensive_result.id_2 AND table1.id_1 =
> \{id}
> In this case, the subquery "expensive_result" is expensive to compute, but it
> doesn't change between queries. The rest of the query does because of the
> \{id} parameter. This means the application can't cache it, but it would be
> good if there was a way to cache expensive_result.
> Note that there is currently a coprocessor based "server cache", but the data
> in this "cache" is not persisted across queries. It is deleted after a TTL
> expires (30sec by default), or when the query completes.
> This is issue is fairly high priority for us at 23andMe and we'd be happy to
> provide a patch with some guidance from Phoenix maintainers. We are currently
> putting together a design document for a solution, and we'll post it to this
> Jira ticket for review in a few days.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
