incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-356) Blur console should ignore queries when table is disabled
Date Mon, 11 Aug 2014 17:18:12 GMT

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

Tim Williams commented on BLUR-356:
-----------------------------------

Locally I just #1, but as you say it creates gobs of requests on the system.  

One thing that came to mind as I was looking into this was that it'd be handy to let the blur-console
wrap the Iface so that it can provide some convenience methods on the client for stuff like
this.  In this case, we could add getEnabledTables() on the wrapped method that, underneath
could cache the tables and catch-and-retry in the event one got disabled.  Similar to #3 but
moving the cached state from the client to the server.  I'm happy with any of them other than
#1 really.

> Blur console should ignore queries when table is disabled
> ---------------------------------------------------------
>
>                 Key: BLUR-356
>                 URL: https://issues.apache.org/jira/browse/BLUR-356
>             Project: Apache Blur
>          Issue Type: Bug
>          Components: Blur Console
>    Affects Versions: 0.2.4
>            Reporter: Tim Williams
>
> When the list of tables in a cluster has a table thats disabled, the console tries to
get the statusid's of its queries.  Since the table is disabled blur responds with a BlurException.
 
> QueryUtil.getQueries should guard the table with an enabled filter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message