incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Avenoso (JIRA)" <>
Subject [jira] [Commented] (BLUR-356) Blur console should ignore queries when table is disabled
Date Sun, 10 Aug 2014 15:37:12 GMT


Andrew Avenoso commented on BLUR-356:

This definitely does appear to be a bug.
I've thought of 3 different ways to fix this.
1 --The simplest would be to query blur and make sure each table is enabled before getting
the queries for it.
My concern with this method is the amount of requests to blur.
2 -- We could add a new call to the blur thrift api to getEnabledTables. This would fix the
problem without doing any more requests, but would require adding to the blur api.
3 -- We could make the ajax call to get queries accept a list of tables to check. The js already
knows which tables are enabled/disabled. This would not require any change to the blur api
and would also reduce the number of calls to blur by one because we'd no longer have to ask
for the list of tables.

I think number 3 is the best choice, but I'd love to get feedback on all the options.

> Blur console should ignore queries when table is disabled
> ---------------------------------------------------------
>                 Key: BLUR-356
>                 URL:
>             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

View raw message