[
https://issues.apache.org/jira/browse/BLUR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron McCurry closed BLUR-345.
------------------------------
Resolution: Fixed
Assignee: Aaron McCurry
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=11a43d7cded3508a5127d1ed83a6ad1dc43fc408
> Update Mutate actions should work correctly for large Rows
> ----------------------------------------------------------
>
> Key: BLUR-345
> URL: https://issues.apache.org/jira/browse/BLUR-345
> Project: Apache Blur
> Issue Type: Bug
> Components: Blur
> Affects Versions: 0.2.2
> Reporter: Tim Williams
> Assignee: Aaron McCurry
> Priority: Critical
>
> There are currently two conditions that cause dropped data in a blur update
> mutate - both related to the configured fetch limits.
> 1) If the row contains more records than the configured property
> [blur.max.records.per.row.fetch.request] anything over that setting would be
> dropped on an update.
> 2) If the row contains large records that exceed the configured max heap size
> [blur.max.heap.per.row.fetch] only records up to that setting would be
> included in the update.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
