incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikrant Navalgund (JIRA)" <>
Subject [jira] [Commented] (BLUR-276) Create an API the allows for server side manipulation of requests
Date Thu, 24 Oct 2013 12:36:01 GMT


Vikrant Navalgund commented on BLUR-276:

Hello Aaron,
Can we have a short discussion/brainstorming on this?

What is the purpose? Is it to provide for role-based access on Tables/Cluster, like tagging
the particular table.
Ex: While creating the table we could also store the meta-data for tagging in ZK like
       a. Is this table containing sensitive info 
       b. What are the columns that have sensitive data
Then on the shard server, before any mutate or query is invoked have a filter pipeline built
from reading the meta-data from ZK and then process the request/response.

I am just thinking out loud here. Can we have more details or any use-case that you have in


> Create an API the allows for server side manipulation of requests
> -----------------------------------------------------------------
>                 Key: BLUR-276
>                 URL:
>             Project: Apache Blur
>          Issue Type: New Feature
>          Components: Blur
>    Affects Versions: 0.3.0
>            Reporter: Aaron McCurry
>             Fix For: 0.3.0
> Create a server side interface that allows for customizing the requests and responses
made to the server.  This should be created in a filter pattern and definable per table or
for the entire system.
> - This could be used for altering mutates before they are indexed.
> - Filtering out data before it's sent back to the client.

This message was sent by Atlassian JIRA

View raw message