Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo, mail # dev - Accumulo 1.6 and beyond feature summit


Copy link to this message
-
Re: Accumulo 1.6 and beyond feature summit
Keith Turner 2013-01-29, 17:38
On Tue, Jan 29, 2013 at 12:34 PM, Christopher <[EMAIL PROTECTED]> wrote:
> Features I'd like to see:
>
> 1. Better user experience for configuration: separate, *non-xml*
> configuration files for separate services, and for clients.
I assume you mean tserver, master, gc etc. when you say separate services?

> 2. Separate packaging for separate services (tservers, monitor, master,
> trace), especially for RPMs and DEBs to make provisioning easier.
> 3. A suite of command-line utilities based on the shell's commands, that
> work in Bash, rather than be restricted to the limitations of the shell to
> issue these commands.
> 4. Provide a script maintained and supported by the community to provision
> an Accumulo cloud instance in EC2 or OpenStack.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Tue, Jan 29, 2013 at 12:15 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> On Mon, Jan 28, 2013 at 7:12 PM, William Slacum
>> <[EMAIL PROTECTED]> wrote:
>> > I'd like to see:
>> >
>> > - Data triggers on insertion
>> > - REST interface for looking up ranges of keys
>> > - A DSL or some other interpreted language for crafting iterators
>> >   - there's the clojure iterator, but something like python (via jython)
>> or
>> > javascript (via rhino) would be more adoptable
>> > - Adding a clean up hook to iterators
>>
>> I was thinking about this.   If we added a close() method to the SKVI
>> interface then it would break existing iterators.  Another option
>> would be to support closing iterators that implement Closeable.  So if
>> in iterators is an intstanceof Closeable then the framework could
>> close it when its finished with the iterator.   I wish there had been
>> a 1.5 ticket for this, I think it would have been fairly simple to
>> implement.
>>
>> > - Allowing iterators to launch connections to other services (caching,
>> > other tservers) to retrieve or write data
>> > - Merging of the batch scanner and scanner implementations
>> >   - a batch scanner with 1 thread have the same behavior as a scanner
>> >   - scanners have a close() method on them
>> > - Adding some builder interface for creating and introspecting iterator
>> > stacks
>> > - Clients being able to scan to specific keys using the scan command
>>