Ed Coleman commented on ACCUMULO-4806:

I am not aware of any issues. From the client's perspective, it would actually 
simplify operations. 

Adding the splits at table creation would make the operations to prepare a 
table for bulk import into a new / pre-split table simpler because it could be 
done in one client operation rather than the current four:  create table, add 
splits, off-line table, online table. Being able to add splits to an off-line 
table would require still require the same number of client operations: create 
table, off-line table, add splits, on-line table, just the order is different.

The currently complexity is manageable, so I would defer to any approach that 
is easier to implement and provides equivalent performance and processing 

For performance I'm measuring wall total wall clock time from when the table is 
created to when it is ready for the bulk import to begin.

For processing, I'm assuming that the processing required for adding splits at 
table creation or to an off-line table would be equivalent and one would not 
require significantly more processing power than the other - especially if the 
operations are performed by the master when it could impact other master 

So, I think from a client perspective adding the spilts at creation time would 
be preferred. 


> Allow offline bulk imports
> --------------------------
>                 Key: ACCUMULO-4806
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4806
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Mark Owens
>            Assignee: Michael Miller
>            Priority: Major
>             Fix For: 2.0.0
> Allowing offline bulk imports would be useful for some customers. Currently 
> these customers already take tables offline to set split points but then have 
> to bring them back online before starting the import.

This message was sent by Atlassian JIRA

Reply via email to