You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@accumulo.apache.org by Josh Elser <jo...@gmail.com> on 2017/01/28 21:16:30 UTC
Re: accumulo enhancement suggestions
Please use the user@accumulo.apache.org mailing list in the future for
these kinds of questions/request. It is not in good taste to send
private emails to those involved in any Apache projects.
--
The functionality you're suggesting already exists for all versions you
mentioned.
http://accumulo.apache.org/1.8/accumulo_user_manual.html#_instance_volumes
Information on contacting those who work on or with Apache Accumulo is
documented at http://accumulo.apache.org/get_involved/.
Matthew Purdy wrote:
> Josh,
>
> I have a simple feature enhancement for accumulo that would help
> developers; is there a place to put in suggestions/requests?
>
>
> =====================
>
> i develop on linux (normally a VM). i would like to install a few
> accumulo versions (1.6.6, 1.7.2, 1.8.0) on the same VM running on the
> same hadoop pseudo cluster all with different zookeeper instances and
> different root directories in hdfs. this way i can turn on the accumulo
> version i want and run my code on that version.
>
> i can configure multiple zookeeper instances; however, accumulo puts all
> its tables in hdfs under /accumulo. it would be nice to configure that
> root path; then i could create /accumulo166, /accumulo172, accumulo180,
> etc and only have to turn on/off different versions of accumulo (once
> they were initially configured in zookeeper)
>
> i don\u2019t think this would be a big change; should only need a new
> property in accumulo-site.xml and expose the root directory using that
> property
>
> =====================
>
> Thank You,
> Matthew Purdy
>
> ------------------------------------------------------------------------------------------------------------------
> Matthew Purdy
> Principle Software Engineer
> Purdy Good Engineering
> matthew.purdy@purdygoodengineering.com
> <ma...@purdygoodengineering.com>
> 443.848.1595
> --------------------------------------
> "Lead, follow, or get out of the way." -- Thomas Paine
> "Make everything as simple as possible, but not simpler." -- Albert Einstein
> "The definition of insanity is doing the same thing over and over and
> expecting a different result." -- Benjamin Franklin
> "We can't solve problems by using the same kind of thinking we used when
> we created them." -- Albert Einstein
> ------------------------------------------------------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
> to Purdy Good Engineering LLC and its affiliates may be contained in
> this message. If you are not a recipient indicated or intended in this
> message (or responsible for delivery of this message to such person), or
> you think for any reason that this message may have been addressed to
> you in error, you may not use or copy or deliver this message to anyone
> else. In such case, you should destroy this message and are asked to
> notify the sender by reply e-mail.
>
Re: accumulo enhancement suggestions
Posted by Keith Turner <ke...@deenlo.com>.
On Mon, Jan 30, 2017 at 4:04 PM, John Vines <vi...@apache.org> wrote:
> From reading the ticket, they want to have different directories in hdfs
Oh yeah, I should have read the email more closely.
> used. We already support this, this is the instance.volumes property
>
>
> On Mon, Jan 30, 2017 at 10:10 AM Keith Turner <ke...@deenlo.com> wrote:
>>
>> One norm we set in Fluo is expecting the user to add a path to the
>> zookeeper connection string. For example a connection string like the
>> following :
>>
>> zserver1:1234,zserver2:1234,zserver3:1234/foo9
>>
>> Would chroot the zookeeper connection to /foo9. So if you listed
>> children a / using that connection, it would actually list children of
>> /foo9.
>>
>> I wonder if these types of connection strings would work with
>> Accumulo? If not it may be worthwhile to fix the issues that prevent
>> it from working. Then you could use this zookeeper feature to
>> accomplish your use case.
>>
>> On Sat, Jan 28, 2017 at 4:16 PM, Josh Elser <jo...@gmail.com> wrote:
>> > Please use the user@accumulo.apache.org mailing list in the future for
>> > these
>> > kinds of questions/request. It is not in good taste to send private
>> > emails
>> > to those involved in any Apache projects.
>> >
>> > --
>> >
>> > The functionality you're suggesting already exists for all versions you
>> > mentioned.
>> >
>> >
>> > http://accumulo.apache.org/1.8/accumulo_user_manual.html#_instance_volumes
>> >
>> > Information on contacting those who work on or with Apache Accumulo is
>> > documented at http://accumulo.apache.org/get_involved/.
>> >
>> > Matthew Purdy wrote:
>> >>
>> >> Josh,
>> >>
>> >> I have a simple feature enhancement for accumulo that would help
>> >> developers; is there a place to put in suggestions/requests?
>> >>
>> >>
>> >> =====================
>> >>
>> >> i develop on linux (normally a VM). i would like to install a few
>> >> accumulo versions (1.6.6, 1.7.2, 1.8.0) on the same VM running on the
>> >> same hadoop pseudo cluster all with different zookeeper instances and
>> >> different root directories in hdfs. this way i can turn on the accumulo
>> >> version i want and run my code on that version.
>> >>
>> >> i can configure multiple zookeeper instances; however, accumulo puts
>> >> all
>> >> its tables in hdfs under /accumulo. it would be nice to configure that
>> >> root path; then i could create /accumulo166, /accumulo172, accumulo180,
>> >> etc and only have to turn on/off different versions of accumulo (once
>> >> they were initially configured in zookeeper)
>> >>
>> >> i don’t think this would be a big change; should only need a new
>> >> property in accumulo-site.xml and expose the root directory using that
>> >> property
>> >>
>> >> =====================
>> >>
>> >> Thank You,
>> >> Matthew Purdy
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------------------------------------------
>> >> Matthew Purdy
>> >> Principle Software Engineer
>> >> Purdy Good Engineering
>> >> matthew.purdy@purdygoodengineering.com
>> >> <ma...@purdygoodengineering.com>
>> >> 443.848.1595
>> >> --------------------------------------
>> >> "Lead, follow, or get out of the way." -- Thomas Paine
>> >> "Make everything as simple as possible, but not simpler." -- Albert
>> >> Einstein
>> >> "The definition of insanity is doing the same thing over and over and
>> >> expecting a different result." -- Benjamin Franklin
>> >> "We can't solve problems by using the same kind of thinking we used
>> >> when
>> >> we created them." -- Albert Einstein
>> >>
>> >>
>> >> ------------------------------------------------------------------------------------------------------------------
>> >>
>> >> CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
>> >> to Purdy Good Engineering LLC and its affiliates may be contained in
>> >> this message. If you are not a recipient indicated or intended in this
>> >> message (or responsible for delivery of this message to such person),
>> >> or
>> >> you think for any reason that this message may have been addressed to
>> >> you in error, you may not use or copy or deliver this message to anyone
>> >> else. In such case, you should destroy this message and are asked to
>> >> notify the sender by reply e-mail.
>> >>
>> >
Re: accumulo enhancement suggestions
Posted by John Vines <vi...@apache.org>.
From reading the ticket, they want to have different directories in hdfs
used. We already support this, this is the instance.volumes property
On Mon, Jan 30, 2017 at 10:10 AM Keith Turner <ke...@deenlo.com> wrote:
> One norm we set in Fluo is expecting the user to add a path to the
> zookeeper connection string. For example a connection string like the
> following :
>
> zserver1:1234,zserver2:1234,zserver3:1234/foo9
>
> Would chroot the zookeeper connection to /foo9. So if you listed
> children a / using that connection, it would actually list children of
> /foo9.
>
> I wonder if these types of connection strings would work with
> Accumulo? If not it may be worthwhile to fix the issues that prevent
> it from working. Then you could use this zookeeper feature to
> accomplish your use case.
>
> On Sat, Jan 28, 2017 at 4:16 PM, Josh Elser <jo...@gmail.com> wrote:
> > Please use the user@accumulo.apache.org mailing list in the future for
> these
> > kinds of questions/request. It is not in good taste to send private
> emails
> > to those involved in any Apache projects.
> >
> > --
> >
> > The functionality you're suggesting already exists for all versions you
> > mentioned.
> >
> >
> http://accumulo.apache.org/1.8/accumulo_user_manual.html#_instance_volumes
> >
> > Information on contacting those who work on or with Apache Accumulo is
> > documented at http://accumulo.apache.org/get_involved/.
> >
> > Matthew Purdy wrote:
> >>
> >> Josh,
> >>
> >> I have a simple feature enhancement for accumulo that would help
> >> developers; is there a place to put in suggestions/requests?
> >>
> >>
> >> =====================
> >>
> >> i develop on linux (normally a VM). i would like to install a few
> >> accumulo versions (1.6.6, 1.7.2, 1.8.0) on the same VM running on the
> >> same hadoop pseudo cluster all with different zookeeper instances and
> >> different root directories in hdfs. this way i can turn on the accumulo
> >> version i want and run my code on that version.
> >>
> >> i can configure multiple zookeeper instances; however, accumulo puts all
> >> its tables in hdfs under /accumulo. it would be nice to configure that
> >> root path; then i could create /accumulo166, /accumulo172, accumulo180,
> >> etc and only have to turn on/off different versions of accumulo (once
> >> they were initially configured in zookeeper)
> >>
> >> i don’t think this would be a big change; should only need a new
> >> property in accumulo-site.xml and expose the root directory using that
> >> property
> >>
> >> =====================
> >>
> >> Thank You,
> >> Matthew Purdy
> >>
> >>
> >>
> ------------------------------------------------------------------------------------------------------------------
> >> Matthew Purdy
> >> Principle Software Engineer
> >> Purdy Good Engineering
> >> matthew.purdy@purdygoodengineering.com
> >> <ma...@purdygoodengineering.com>
> >> 443.848.1595 <(443)%20848-1595>
> >> --------------------------------------
> >> "Lead, follow, or get out of the way." -- Thomas Paine
> >> "Make everything as simple as possible, but not simpler." -- Albert
> >> Einstein
> >> "The definition of insanity is doing the same thing over and over and
> >> expecting a different result." -- Benjamin Franklin
> >> "We can't solve problems by using the same kind of thinking we used when
> >> we created them." -- Albert Einstein
> >>
> >>
> ------------------------------------------------------------------------------------------------------------------
> >>
> >> CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
> >> to Purdy Good Engineering LLC and its affiliates may be contained in
> >> this message. If you are not a recipient indicated or intended in this
> >> message (or responsible for delivery of this message to such person), or
> >> you think for any reason that this message may have been addressed to
> >> you in error, you may not use or copy or deliver this message to anyone
> >> else. In such case, you should destroy this message and are asked to
> >> notify the sender by reply e-mail.
> >>
> >
>
Re: accumulo enhancement suggestions
Posted by Keith Turner <ke...@deenlo.com>.
One norm we set in Fluo is expecting the user to add a path to the
zookeeper connection string. For example a connection string like the
following :
zserver1:1234,zserver2:1234,zserver3:1234/foo9
Would chroot the zookeeper connection to /foo9. So if you listed
children a / using that connection, it would actually list children of
/foo9.
I wonder if these types of connection strings would work with
Accumulo? If not it may be worthwhile to fix the issues that prevent
it from working. Then you could use this zookeeper feature to
accomplish your use case.
On Sat, Jan 28, 2017 at 4:16 PM, Josh Elser <jo...@gmail.com> wrote:
> Please use the user@accumulo.apache.org mailing list in the future for these
> kinds of questions/request. It is not in good taste to send private emails
> to those involved in any Apache projects.
>
> --
>
> The functionality you're suggesting already exists for all versions you
> mentioned.
>
> http://accumulo.apache.org/1.8/accumulo_user_manual.html#_instance_volumes
>
> Information on contacting those who work on or with Apache Accumulo is
> documented at http://accumulo.apache.org/get_involved/.
>
> Matthew Purdy wrote:
>>
>> Josh,
>>
>> I have a simple feature enhancement for accumulo that would help
>> developers; is there a place to put in suggestions/requests?
>>
>>
>> =====================
>>
>> i develop on linux (normally a VM). i would like to install a few
>> accumulo versions (1.6.6, 1.7.2, 1.8.0) on the same VM running on the
>> same hadoop pseudo cluster all with different zookeeper instances and
>> different root directories in hdfs. this way i can turn on the accumulo
>> version i want and run my code on that version.
>>
>> i can configure multiple zookeeper instances; however, accumulo puts all
>> its tables in hdfs under /accumulo. it would be nice to configure that
>> root path; then i could create /accumulo166, /accumulo172, accumulo180,
>> etc and only have to turn on/off different versions of accumulo (once
>> they were initially configured in zookeeper)
>>
>> i don’t think this would be a big change; should only need a new
>> property in accumulo-site.xml and expose the root directory using that
>> property
>>
>> =====================
>>
>> Thank You,
>> Matthew Purdy
>>
>>
>> ------------------------------------------------------------------------------------------------------------------
>> Matthew Purdy
>> Principle Software Engineer
>> Purdy Good Engineering
>> matthew.purdy@purdygoodengineering.com
>> <ma...@purdygoodengineering.com>
>> 443.848.1595
>> --------------------------------------
>> "Lead, follow, or get out of the way." -- Thomas Paine
>> "Make everything as simple as possible, but not simpler." -- Albert
>> Einstein
>> "The definition of insanity is doing the same thing over and over and
>> expecting a different result." -- Benjamin Franklin
>> "We can't solve problems by using the same kind of thinking we used when
>> we created them." -- Albert Einstein
>>
>> ------------------------------------------------------------------------------------------------------------------
>>
>> CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
>> to Purdy Good Engineering LLC and its affiliates may be contained in
>> this message. If you are not a recipient indicated or intended in this
>> message (or responsible for delivery of this message to such person), or
>> you think for any reason that this message may have been addressed to
>> you in error, you may not use or copy or deliver this message to anyone
>> else. In such case, you should destroy this message and are asked to
>> notify the sender by reply e-mail.
>>
>