[jira] [Commented] (ASTERIXDB-2386) Metadata cache should be refreshed after a cluster restart.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ASTERIXDB-2386:
------------------------------------------------------------

Commit 2fd212329e28e45f1505f185753ae3466d880b39 in asterixdb's branch refs/heads/master from Till Westmann
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2fd2123 ]

[ASTERIXDB-2386][CLUS] Allow extension of the global recovery manager

Allow the Asterix GlobalRecoveryManager to be extended
Cleanup some deployed job spec methods

Change-Id: I1213e702a77ededde18ee0b50bc105212f43480d
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2640
Reviewed-by: Till Westmann <ti...@apache.org>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Steven Jacobs <sj...@ucr.edu>


> Metadata cache should be refreshed after a cluster restart.
> -----------------------------------------------------------
>
>                 Key: ASTERIXDB-2386
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2386
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>            Reporter: Steven Jacobs
>            Priority: Major
>
> After a cluster restart, queries that don't first call "use" on the dataverses involved will fail. This is because they aren't found in the metadata cache. The bug can be reproduced as follows:
> drop dataverse channels if exists;
> create dataverse channels;
> use channels;
> create type TweetMessageTypeuuid as closed {
>  tweetid: uuid,
>  sender_location: point,
>  send_time: datetime,
>  referred_topics: \{{ string }},
>  message_text: string,
>  countA: int32,
>  countB: int32
> };
> create dataset TweetMessageuuids(TweetMessageTypeuuid)
> primary key tweetid autogenerated;
> create function NearbyTweetsContainingText(place, text) {
>  (select m.message_text
>  from TweetMessageuuids m
>  where contains(m.message_text,text)
>  and spatial_intersect(m.sender_location, place))
> };
>  
> restart the cluster
> Then try the following:
> channels.NearbyTweetsContainingText("hello","world"); 
>  
> It works fine if you do this instead, because channels gets added to the cache:
> use channels;
> channels.NearbyTweetsContainingText("hello","world");
>  
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)