> On Dec. 13, 2016, 11:11 p.m., Eric Shu wrote:
> > geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb,
> >  line 44
> > <https://reviews.apache.org/r/54723/diff/1/?file=1583275#file1583275line44>
> >
> >     Product may throw TransactionDataRebalancedException instead of 
> > TransactionDataNotColocatedException. Do we need to specify exact exception?

Wording changed to say that there will be an exception, but not which exception.

I'll rebase the second commit before merging to develop.


- Karen


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54723/#review159073
-----------------------------------------------------------


On Dec. 14, 2016, 4:33 p.m., Karen Miller wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54723/
> -----------------------------------------------------------
> 
> (Updated Dec. 14, 2016, 4:33 p.m.)
> 
> 
> Review request for geode, Dave Barnes, Eric Shu, and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> -------
> 
> - First operation to a transactional system which has colocated
> data and replicated/distributed regions must be to a
> partitioned region (with colocated data), to set the transaction
> host.  Note that this was already documented, but not in a
> prominent place.  Now the basics of this info is repeated in
> a less-buried location.
> - Fixed poorly-working links within the subnav and fixed a
> couple of markdown errors.  The errors were improperly
> specified anchor tags.
> 
> 
> Diffs
> -----
> 
>   
> geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb
>  d96de82fa7d5f4074c88863c1732363530c12d39 
> 
> Diff: https://reviews.apache.org/r/54723/diff/
> 
> 
> Testing
> -------
> 
> gradle rat check passes
> 
> Geode book builds with no broken links
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Reply via email to