Tim Williams created BLUR-397:
---------------------------------
Summary: Improve data loading from M/R
Key: BLUR-397
URL: https://issues.apache.org/jira/browse/BLUR-397
Project: Apache Blur
Issue Type: Improvement
Components: Blur, Blur MapReduce
Reporter: Tim Williams
There's an awkward permissions dilemma when writing data into Blur from
Map/Reduce.
A job would typically create a table, then load the data. The challenge is
that the table itself is created through the controller, which means it's
written to DFS as the user actually running the controller daemon - typically
'blur'. The Map/Reduce job may be run as some other user totally, but it may
be a user that you don't want to have write access inside blur's directory
paths. In other words, you'd like arbitrary user(s) to be able to
create/populate table data without necessarily having write access to blur's
internal stuffs.
One approach is to have the user's job write to any location they have access
to, the "tell" Blur to 'import' it - at which time, Blur would literally move
the data into it's control.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
