[
https://issues.apache.org/jira/browse/BLUR-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729727#comment-14729727
]
Tom Hood commented on BLUR-441:
-------------------------------
It turns out we will be upgrading to a version of 0.2.4-rc1 that was grabbed as
of 7/9/2015 in the first couple weeks of 10/2015. Deployment of the feature
impacted by this issue has been pushed out to probably sometime in 11/2015.
Before then, we would like confirmation from you that the root cause of the
corruption is understand and has been fixed. What's your schedule look like
for getting a chance to look into this issue?
I'm not sure how many companies are using blur in a production environment, but
I'm wondering if it's worthwhile your sending an email to notify them of this
corruption issue. In our case at least, the merging of records from multiple
rows into one is a security problem, because the individual rows can have
different security access tags. On the plus side, if it is an issue for more
people, then there might be additional resources available to investigate the
issue. On the other hand, there was the original email I sent to blur-users
about this, so I guess that could count as enough of a notification. Anyway,
just a thought.
> Row Mutation Bug
> ----------------
>
> Key: BLUR-441
> URL: https://issues.apache.org/jira/browse/BLUR-441
> Project: Apache Blur
> Issue Type: Bug
> Components: Blur
> Affects Versions: 0.2.4
> Reporter: Aaron McCurry
> Assignee: Aaron McCurry
> Priority: Blocker
> Fix For: 0.2.4
>
> Attachments: BlurMutationBug.java
>
>
> Reported on blur-user mail list:
> http://mail-archives.apache.org/mod_mbox/incubator-blur-user/201508.mbox/<CABO0Qi6m6xR60R64XBpoq7T0Q4GxxAJDcetV_-6PAmg32FdNxg%40mail.gmail.com>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
