[
https://issues.apache.org/jira/browse/PHOENIX-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155350#comment-15155350
]
James Taylor commented on PHOENIX-2697:
---------------------------------------
It'd be fine for the next release (4.7.1 or 4.8.0). Since it's 100%
client-side, it'd be fine in a 4.7.1 release.
4.x-HBase-0.98 is used to release the 0.98 compatible releases for 4.5, 4.6,
4.7, etc.
4.x-HBase-1.0 is used to release the 1.0 compatible releases for 4.5, 4.6, 4.7,
etc.
master is used to release the 1.1+ compatible releases for 4.5, 4.6, 4.7, etc.
We create a 4.6-HBase-0.98, 4.6-HBase-1.0, and 4.6-HBase-1.1 branch upon
release of the 4.6 release so that in the event there is user demand for patch
releases (and an RM willing to step up) we have a branch on which to commit
fixes.
Our typical modus operandi has been to continue active development on the 4.x
and master branches to minimize back porting while ensuring that we maintain
backward compatibility with previous minor releases such that users can upgrade
through a rolling restart. Our contract
(http://phoenix.apache.org/upgrading.html) is to support two minor releases
back, but for 4.7 we've tested back as far as 4.4.
> Provide a SERIAL hint
> ---------------------
>
> Key: PHOENIX-2697
> URL: https://issues.apache.org/jira/browse/PHOENIX-2697
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Minor
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2697-4.6.txt
>
>
> Sometime it is useful to force a query to executed serially.
> For example a user might want to run a query which is not latency sensitive
> to him/her. In that case providing the SERIAL hint puts less load on the
> HBase cluster and impact other more latency sensitive queries less.
> (In my case I want to use this for testing.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
