incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Hood (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BLUR-441) Row Mutation Bug
Date Wed, 02 Sep 2015 02:35:45 GMT

    [ https://issues.apache.org/jira/browse/BLUR-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726605#comment-14726605
] 

Tom Hood edited comment on BLUR-441 at 9/2/15 2:35 AM:
-------------------------------------------------------

That's good news!  Glad to hear you were able to reproduce the problem.

If you haven't had a chance yet to look into why the corruption was occurring and confirm
the bug is fixed in 0.2.4-rc1 and master, I think that would be a good next step.

Once the problem is understood, let me know if there is an easy workaround short of upgrading
blur.  If there is a quick workaround, that would be good, because we've delayed deployment
of a particular feature to our users due to this blur issue. Otherwise, I'll discuss with
management on a possible timeline for upgrading to a newer blur version if that's the only
solution.  I assume 0.2.4-rc1 would be the most stable one to take?

I'm confused on the exact version of blur we're running at work.  Is there something logged
in the startup of a shard or controller that will tell be a build version/timestamp and/or
tag?

Around 12/15/2014 we upgraded to a version of blur calling itself "0.2.4" (i.e. the jars have
0.2.4 in them).  I'm thinking that it was an earlier version of what is currently in the 0.2.4-rc1.
 I will have to ask around to see when the jars and/or code were downloaded to our network.

I can also check when the version of 0.2.4 on my laptop was downloaded since it exhibits the
problem.  However, I don't remember if I have the source for that version or just the jars.
 I will check.


was (Author: tom hood):
That's good news!  Glad to hear you were able to reproduce the problem.

If you haven't had a chance yet to look into why the corruption was occurring and confirm
the bug is fixed in 0.2.4-rc1 and master, I think that would be a good next step.

Once the problem is understood, let me know if there is an easy workaround short of upgrading
blur.  If there is a quick workaround, that would be good, because we've delayed deployment
of a particular feature to our users due to this blur issue. Otherwise, I'll discuss with
management on a possible timeline for upgrading to a newer blur version if that's the only
solution.  I assume 0.2.4-rc1 would be the most stable one to take?

I'm confused on the exact version of blur we're running at work.  Is there something logged
in the startup of a shard or controller that will tell be a build version/timestamp and/or
tag?

Sometime in 1/2015 (maybe late 2014?) we upgraded to a version of blur calling itself "0.2.4"
(i.e. the jars have 0.2.4 in them).  I'm thinking that it was an earlier version of what is
currently in the 0.2.4-rc1.  I will have to ask around to see when the jars and/or code were
downloaded to our network.

I can also check when the version of 0.2.4 on my laptop was downloaded since it exhibits the
problem.  However, I don't remember if I have the source for that version or just the jars.
 I will check.

> 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)

Mime
View raw message