accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2331) TableConfiguration should override invalidateCache
Date Fri, 07 Feb 2014 16:24:24 GMT

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

ASF subversion and git services commented on ACCUMULO-2331:
-----------------------------------------------------------

Commit 510140ad0cae2d54bc4c097c94cf4b024f3655bf in branch refs/heads/1.6.0-SNAPSHOT from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=510140a ]

ACCUMULO-2331 Actually invalidate the cache in TableConfiguration when requested.

TableConfiguration previously didn't override invalidateCache, which means that
the implementations that used it and the invalidateCache method, were not providing
the semantics that were intended. Fix the case in SimpleTest that outlined this issue,
removing the additional poll/check loop as it was both broken and unnecessary with
proper API implementation.


> TableConfiguration should override invalidateCache
> --------------------------------------------------
>
>                 Key: ACCUMULO-2331
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2331
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.5.1, 1.6.0
>
>
> In trying to get ACCUMULO-1908 resolved, I noticed that I had a new test failure in which
the test appeared to not see updates to a table's properties.
> Upon further investigation, I noticed that the server-side impl in ClientServiceHandler
was calling invalidateCache on the AccumuloConfiguration it was passed (which is actually
a TableConfiguration). However, since this method isn't implemented in TableConfiguration,
the cache wasn't cleared and the client saw stale data.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message