Congratulations on HBase 0.90.0 release!

There are some open questions about HBase at Quora, and this one is asking for the roadmap.
http://www.quora.com/What-are-the-development-plans-for-HBase

Our roadmap on the wiki is outdated, and I think one in the JIRA is not allowing us to get a big picture like master rewrites, shell update, bloom filter, replication, coprocessor and access control.

http://wiki.apache.org/hadoop/HBase/RoadMaps

I would be really happy if the roadmap is updated.

Thanks,
Tatsuya

--
Tatsuya Kawano
Tokyo, Japan

Hey Tatsuya:

Yeah, our RoadMaps were way stale.  I did a quick cleanup.

I think we've learned that RoadMapping at anything but the coarsest of
granularities is a fairly useless exercise.  Folks will work on what
they need.  Figuring what that list is up front is a bit tough to
nail.

That said, as I understand it, the plan for 0.92 is for it to come out
soon.  Very soon.  Its salient feature will be the addition of
Coprocessors.  CPs are already in HBase TRUNK so I don't see anything
getting in the way of a 0.92 in the near term.  Otherwise, the current
set of (unedited) 0.92 issues seems like bug fixes, correctness and
performance: http://su.pr/1rYx71

Thanks,
St.Ack
On Wed, Jan 19, 2011 at 2:32 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>
> Congratulations on HBase 0.90.0 release!
>
> There are some open questions about HBase at Quora, and this one is asking for the roadmap.
> http://www.quora.com/What-are-the-development-plans-for-HBase
>
> Our roadmap on the wiki is outdated, and I think one in the JIRA is not allowing us to get a big picture like master rewrites, shell update, bloom filter, replication, coprocessor and access control.
>
> http://wiki.apache.org/hadoop/HBase/RoadMaps
>
> I would be really happy if the roadmap is updated.
>
> Thanks,
> Tatsuya
>
> --
> Tatsuya Kawano
> Tokyo, Japan
>
>

Thanks, Stack.

Actually, I like the granularity of the updated list. Those few-words summary helps me when I look at the Jira road map, and each Jira ticket helps me to understand what's exactly going on.

Why don't we just have one road map page by now? We could replace the tag lines on Jira road map with the ones on the wiki page, and then make the wiki page obsolete.

- Tatsuya

--
Tatsuya Kawano
Tokyo, Japan
On Jan 20, 2011, at 9:04 AM, Stack <[EMAIL PROTECTED]> wrote:

> Hey Tatsuya:
>
> Yeah, our RoadMaps were way stale.  I did a quick cleanup.
>
> I think we've learned that RoadMapping at anything but the coarsest of
> granularities is a fairly useless exercise.  Folks will work on what
> they need.  Figuring what that list is up front is a bit tough to
> nail.
>
> That said, as I understand it, the plan for 0.92 is for it to come out
> soon.  Very soon.  Its salient feature will be the addition of
> Coprocessors.  CPs are already in HBase TRUNK so I don't see anything
> getting in the way of a 0.92 in the near term.  Otherwise, the current
> set of (unedited) 0.92 issues seems like bug fixes, correctness and
> performance: http://su.pr/1rYx71
>
> Thanks,
> St.Ack
>
>
> On Wed, Jan 19, 2011 at 2:32 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>>
>> Congratulations on HBase 0.90.0 release!
>>
>> There are some open questions about HBase at Quora, and this one is asking for the roadmap.
>> http://www.quora.com/What-are-the-development-plans-for-HBase
>>
>> Our roadmap on the wiki is outdated, and I think one in the JIRA is not allowing us to get a big picture like master rewrites, shell update, bloom filter, replication, coprocessor and access control.
>>
>> http://wiki.apache.org/hadoop/HBase/RoadMaps
>>
>> I would be really happy if the roadmap is updated.
>>
>> Thanks,
>> Tatsuya
>>
>> --
>> Tatsuya Kawano
>> Tokyo, Japan
>>
>>

I like your suggestion.  Then there is just one list, the one we
actually are keeping up and implementing.  Want to have a go at it
Tatsuya?  Otherwise I will.

Good on you,
St.Ack

On Wed, Jan 19, 2011 at 7:41 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>
> Thanks, Stack.
>
> Actually, I like the granularity of the updated list. Those few-words summary helps me when I look at the Jira road map, and each Jira ticket helps me to understand what's exactly going on.
>
> Why don't we just have one road map page by now? We could replace the tag lines on Jira road map with the ones on the wiki page, and then make the wiki page obsolete.
>
> - Tatsuya
>
> --
> Tatsuya Kawano
> Tokyo, Japan
>
>
> On Jan 20, 2011, at 9:04 AM, Stack <[EMAIL PROTECTED]> wrote:
>
>> Hey Tatsuya:
>>
>> Yeah, our RoadMaps were way stale.  I did a quick cleanup.
>>
>> I think we've learned that RoadMapping at anything but the coarsest of
>> granularities is a fairly useless exercise.  Folks will work on what
>> they need.  Figuring what that list is up front is a bit tough to
>> nail.
>>
>> That said, as I understand it, the plan for 0.92 is for it to come out
>> soon.  Very soon.  Its salient feature will be the addition of
>> Coprocessors.  CPs are already in HBase TRUNK so I don't see anything
>> getting in the way of a 0.92 in the near term.  Otherwise, the current
>> set of (unedited) 0.92 issues seems like bug fixes, correctness and
>> performance: http://su.pr/1rYx71
>>
>> Thanks,
>> St.Ack
>>
>>
>> On Wed, Jan 19, 2011 at 2:32 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>>>
>>> Congratulations on HBase 0.90.0 release!
>>>
>>> There are some open questions about HBase at Quora, and this one is asking for the roadmap.
>>> http://www.quora.com/What-are-the-development-plans-for-HBase
>>>
>>> Our roadmap on the wiki is outdated, and I think one in the JIRA is not allowing us to get a big picture like master rewrites, shell update, bloom filter, replication, coprocessor and access control.
>>>
>>> http://wiki.apache.org/hadoop/HBase/RoadMaps
>>>
>>> I would be really happy if the roadmap is updated.
>>>
>>> Thanks,
>>> Tatsuya
>>>
>>> --
>>> Tatsuya Kawano
>>> Tokyo, Japan
>>>
>>>
>

Hi Stack,

Please go ahead and edit them for me? I only have read access to the release descriptions on Jira.

Thank you,

p.s.
Also, can you please assign HBASE-3391 to me?

--
Tatsuya Kawano
Tokyo, Japan
On Jan 20, 2011, at 3:10 PM, Stack <[EMAIL PROTECTED]> wrote:

> I like your suggestion.  Then there is just one list, the one we
> actually are keeping up and implementing.  Want to have a go at it
> Tatsuya?  Otherwise I will.
>
> Good on you,
> St.Ack
>
> On Wed, Jan 19, 2011 at 7:41 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>>
>> Thanks, Stack.
>>
>> Actually, I like the granularity of the updated list. Those few-words summary helps me when I look at the Jira road map, and each Jira ticket helps me to understand what's exactly going on.
>>
>> Why don't we just have one road map page by now? We could replace the tag lines on Jira road map with the ones on the wiki page, and then make the wiki page obsolete.
>>
>> - Tatsuya
>>
>> --
>> Tatsuya Kawano
>> Tokyo, Japan
>>
>>
>> On Jan 20, 2011, at 9:04 AM, Stack <[EMAIL PROTECTED]> wrote:
>>
>>> Hey Tatsuya:
>>>
>>> Yeah, our RoadMaps were way stale.  I did a quick cleanup.
>>>
>>> I think we've learned that RoadMapping at anything but the coarsest of
>>> granularities is a fairly useless exercise.  Folks will work on what
>>> they need.  Figuring what that list is up front is a bit tough to
>>> nail.
>>>
>>> That said, as I understand it, the plan for 0.92 is for it to come out
>>> soon.  Very soon.  Its salient feature will be the addition of
>>> Coprocessors.  CPs are already in HBase TRUNK so I don't see anything
>>> getting in the way of a 0.92 in the near term.  Otherwise, the current
>>> set of (unedited) 0.92 issues seems like bug fixes, correctness and
>>> performance: http://su.pr/1rYx71
>>>
>>> Thanks,
>>> St.Ack
>>>
>>>
>>> On Wed, Jan 19, 2011 at 2:32 PM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>>>>
>>>> Congratulations on HBase 0.90.0 release!
>>>>
>>>> There are some open questions about HBase at Quora, and this one is asking for the roadmap.
>>>> http://www.quora.com/What-are-the-development-plans-for-HBase
>>>>
>>>> Our roadmap on the wiki is outdated, and I think one in the JIRA is not allowing us to get a big picture like master rewrites, shell update, bloom filter, replication, coprocessor and access control.
>>>>
>>>> http://wiki.apache.org/hadoop/HBase/RoadMaps
>>>>
>>>> I would be really happy if the roadmap is updated.
>>>>
>>>> Thanks,
>>>> Tatsuya
>>>>
>>>> --
>>>> Tatsuya Kawano
>>>> Tokyo, Japan
>>>>
>>>>
>>

On Thu, Jan 20, 2011 at 2:58 AM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
> Hi Stack,
>
> Please go ahead and edit them for me? I only have read access to the release descriptions on Jira.
>
So I edited up the 0.92 description.  RoadMap looks like this now:

https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
(I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
Its going in what is probably the order in which we should make these
releases.

How does that look Tatsuya?  I changed the hbase main wiki page to
point to JIRA and marked the old roadmap 'obsolete'.

What you think?
>
> p.s.
> Also, can you please assign HBASE-3391 to me?
>
>

Pardon me.  I did not realize you were not an HBase contributor.  You
earned it long time ago.   Sorry about that.  I fixed it up in JIRA
and assigned you the issue.  You should be able to do edits up in JIRA
now.   Let me know if its not working for you.

Thanks,
St.Ack

I didn't know this view existed in jira. Nice.

I think we can drop 0.20.7. Would anyone recommend its use?

    - Andy
> From: Stack <[EMAIL PROTECTED]>
> Subject: Re: HBase roadmaps
> To: [EMAIL PROTECTED]
> Date: Thursday, January 20, 2011, 9:55 PM
> So I edited up the 0.92 description.  RoadMap looks
> like this now:
>
> https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>
> Its showing 0.20.7, then 0.90.1, then 0.92.0.  You
> think that right?
> (I wonder if we are going to do a 0.20.7 -- maybe I should
> drop it?).

+1 on dropping 0.20.7

> -----Original Message-----
> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 20, 2011 10:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: HBase roadmaps
>
> I didn't know this view existed in jira. Nice.
>
> I think we can drop 0.20.7. Would anyone recommend its use?
>
>     - Andy
>
>
> > From: Stack <[EMAIL PROTECTED]>
> > Subject: Re: HBase roadmaps
> > To: [EMAIL PROTECTED]
> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
> > description.  RoadMap looks like this now:
> >
> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.
> > plugin.system.project:roadmap-panel
> >
> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>
>
>
>

Hi Stack,

> So I edited up the 0.92 description.  RoadMap looks like this now:
>
> https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
It looks good to me. Thank you for updating it.
> Pardon me.  I did not realize you were not an HBase contributor

Don't be sorry. It's just because I've only reported issues and never worked on them by myself. Now I see a bunch more options on Jira!

Thanks,

--
Tatsuya Kawano
Tokyo, Japan
On Jan 21, 2011, at 2:55 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Thu, Jan 20, 2011 at 2:58 AM, Tatsuya Kawano <[EMAIL PROTECTED]> wrote:
>> Hi Stack,
>>
>> Please go ahead and edit them for me? I only have read access to the release descriptions on Jira.
>>
> So I edited up the 0.92 description.  RoadMap looks like this now:
>
> https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>
> Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
> (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
> Its going in what is probably the order in which we should make these
> releases.
>
> How does that look Tatsuya?  I changed the hbase main wiki page to
> point to JIRA and marked the old roadmap 'obsolete'.
>
> What you think?
>
>
>>
>> p.s.
>> Also, can you please assign HBASE-3391 to me?
>>
>>
>
> Pardon me.  I did not realize you were not an HBase contributor.  You
> earned it long time ago.   Sorry about that.  I fixed it up in JIRA
> and assigned you the issue.  You should be able to do edits up in JIRA
> now.   Let me know if its not working for you.
>
> Thanks,
> St.Ack

Hello.
first of all, thanks to hbase members so much ,
you helped me a lot.

I wrote simple jdo module for hbase newbie. I wish this module can help
them.

Some features

   - simple jdo(used reflection)
   - HTable pool ( I already know HTablePool in habse )
   - simple query classes ( insert,delete,update,select)
   - some convinent mehtods.
   - table sequence generator

I want to contribute this module to hbase
absolutely, I'll do upgrade that more than more.

again, thanks for help.

http://code.google.com/p/hbase-jdo/  (you can download sources here)
---------------------------------------------

AbstractHBaseDBO dbo = new HBaseDBOImpl();

//drop if table is already exist. if(dbo.isTableExist("user")){
dbo.deleteTable("user");
}

//create table dbo.createTableIfNotExist("user",HBaseOrder.DESC,"account");
//dbo.createTableIfNotExist("user",HBaseOrder.ASC,"account");
//create index. String[] cols={"id","name"};
dbo.addIndexExistingTable("user","account",cols);

//insert InsertQuery insert = dbo.createInsertQuery("user");
UserBean bean = new UserBean();
bean.setFamily("account");
bean.setAge(20);
bean.setEmail("[EMAIL PROTECTED]");
bean.setId("ncanis");
bean.setName("ncanis");
bean.setPassword("1111");
insert.insert(bean);

//select 1 row SelectQuery select = dbo.createSelectQuery("user");
UserBean resultBean = (UserBean)select.select(bean.getRow(),UserBean.class);

// select column value. String value (String)select.selectColumn(bean.getRow(),"account","id",String.class);

// search with option (QSearch has EQUAL, NOT_EQUAL, LIKE) //
select id,password,name,email from account where id='ncanis' limit
startRow,20 HBaseParam param = new HBaseParam();
param.setPage(bean.getRow(),20);
param.addColumn("id","password","name","email");
param.addSearchOption("id","ncanis",QSearch.EQUAL);
select.search("account", param, UserBean.class);

// search column value is existing. boolean isExist select.existColumnValue("account","id","ncanis".getBytes());

// update password. UpdateQuery update = dbo.createUpdateQuery("user");
Hashtable<String, byte[]> colsTable = new Hashtable<String, byte[]>();
colsTable.put("password","2222".getBytes());
update.update(bean.getRow(),"account",colsTable);

//delete DeleteQuery delete = dbo.createDeleteQuery("user");
delete.deleteRow(resultBean.getRow());

//////////////////////////////////// // etc
// HTable pool with apache commons pool // borrow and release.
HBasePoolManager(maxActive, minIdle etc..) IndexedTable table dbo.getPool().borrow("user");
dbo.getPool().release(table);

// upload bigFile by hadoop directly. HBaseBigFile bigFile = new
HBaseBigFile();
File file = new File("doc/movie.avi");
FileInputStream fis = new FileInputStream(file);
Path rootPath = new Path("/files/");
String filename = "movie.avi";
bigFile.uploadFile(rootPath,filename,fis,true);

// receive file stream from hadoop. Path p = new Path(rootPath,filename);
InputStream is = bigFile.path2Stream(p,4096);

+1 on dropping and I like the JIRA based roadmap, but it is somewhat
hard to read for others. Would there be a way to use super/uber issues
for the main goals and then add the others underneath? I do not think
the priority etc. is good for that as a bug fix being a blocker rather
falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
bureaucratic request and may be overkill and also not what JIRA is
for. I am just asking as it would be nice to condense fixes into the
major goals for a release.

On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
> +1 on dropping 0.20.7
>
>> -----Original Message-----
>> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, January 20, 2011 10:14 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: HBase roadmaps
>>
>> I didn't know this view existed in jira. Nice.
>>
>> I think we can drop 0.20.7. Would anyone recommend its use?
>>
>>     - Andy
>>
>>
>> > From: Stack <[EMAIL PROTECTED]>
>> > Subject: Re: HBase roadmaps
>> > To: [EMAIL PROTECTED]
>> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>> > description.  RoadMap looks like this now:
>> >
>> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira.
>> > plugin.system.project:roadmap-panel
>> >
>> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>>
>>
>>
>>
>

It is possible to do (but a pain) by setting up the smaller tasks as
sub-tasks on major bugs and then only setting the version for the major
bugs.

I don't like doing that so much since it is fairly intricate.  If you have a
marker for majorness, you can probably build a custom report to do the job
as well.

On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:

> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
> hard to read for others. Would there be a way to use super/uber issues
> for the main goals and then add the others underneath? I do not think
> the priority etc. is good for that as a bug fix being a blocker rather
> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
> bureaucratic request and may be overkill and also not what JIRA is
> for. I am just asking as it would be nice to condense fixes into the
> major goals for a release.
>
> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
> > +1 on dropping 0.20.7
> >
> >> -----Original Message-----
> >> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
> >> Sent: Thursday, January 20, 2011 10:14 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: HBase roadmaps
> >>
> >> I didn't know this view existed in jira. Nice.
> >>
> >> I think we can drop 0.20.7. Would anyone recommend its use?
> >>
> >>     - Andy
> >>
> >>
> >> > From: Stack <[EMAIL PROTECTED]>
> >> > Subject: Re: HBase roadmaps
> >> > To: [EMAIL PROTECTED]
> >> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
> >> > description.  RoadMap looks like this now:
> >> >
> >> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
> .
> >> > plugin.system.project:roadmap-panel
> >> >
> >> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
> >> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
> >>
> >>
> >>
> >>
> >
>

I like Ted's suggestion.  We could add a tag for
"release-wont-happen-w/o-this-fix" and then make custom report.  Ain't
sure how to make that happen under the roadmap tag in JIRA though.

I'll drop 0.20.7.  I too don't see any of us pushing it out.  I'll
weed 0.90.1 a bit too (add stuff back in if I eject something that
should be kept in).

St.Ack

On Fri, Jan 21, 2011 at 7:30 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
> It is possible to do (but a pain) by setting up the smaller tasks as
> sub-tasks on major bugs and then only setting the version for the major
> bugs.
>
> I don't like doing that so much since it is fairly intricate.  If you have a
> marker for majorness, you can probably build a custom report to do the job
> as well.
>
> On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>
>> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
>> hard to read for others. Would there be a way to use super/uber issues
>> for the main goals and then add the others underneath? I do not think
>> the priority etc. is good for that as a bug fix being a blocker rather
>> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
>> bureaucratic request and may be overkill and also not what JIRA is
>> for. I am just asking as it would be nice to condense fixes into the
>> major goals for a release.
>>
>> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
>> > +1 on dropping 0.20.7
>> >
>> >> -----Original Message-----
>> >> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>> >> Sent: Thursday, January 20, 2011 10:14 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: Re: HBase roadmaps
>> >>
>> >> I didn't know this view existed in jira. Nice.
>> >>
>> >> I think we can drop 0.20.7. Would anyone recommend its use?
>> >>
>> >>     - Andy
>> >>
>> >>
>> >> > From: Stack <[EMAIL PROTECTED]>
>> >> > Subject: Re: HBase roadmaps
>> >> > To: [EMAIL PROTECTED]
>> >> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>> >> > description.  RoadMap looks like this now:
>> >> >
>> >> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
>> .
>> >> > plugin.system.project:roadmap-panel
>> >> >
>> >> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>> >> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>> >>
>> >>
>> >>
>> >>
>> >
>>
>

I was assuming it is not easy - a lot of stuff on JIRA is somewhat
convoluted. But I like the tag idea to flag major work, i.e. that
would be compiled in JIRA or externally to build the list for the top
level roadmap.

On Fri, Jan 21, 2011 at 3:43 PM, Stack <[EMAIL PROTECTED]> wrote:
> I like Ted's suggestion.  We could add a tag for
> "release-wont-happen-w/o-this-fix" and then make custom report.  Ain't
> sure how to make that happen under the roadmap tag in JIRA though.
>
> I'll drop 0.20.7.  I too don't see any of us pushing it out.  I'll
> weed 0.90.1 a bit too (add stuff back in if I eject something that
> should be kept in).
>
> St.Ack
>
> On Fri, Jan 21, 2011 at 7:30 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
>> It is possible to do (but a pain) by setting up the smaller tasks as
>> sub-tasks on major bugs and then only setting the version for the major
>> bugs.
>>
>> I don't like doing that so much since it is fairly intricate.  If you have a
>> marker for majorness, you can probably build a custom report to do the job
>> as well.
>>
>> On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>>
>>> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
>>> hard to read for others. Would there be a way to use super/uber issues
>>> for the main goals and then add the others underneath? I do not think
>>> the priority etc. is good for that as a bug fix being a blocker rather
>>> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
>>> bureaucratic request and may be overkill and also not what JIRA is
>>> for. I am just asking as it would be nice to condense fixes into the
>>> major goals for a release.
>>>
>>> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
>>> > +1 on dropping 0.20.7
>>> >
>>> >> -----Original Message-----
>>> >> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>>> >> Sent: Thursday, January 20, 2011 10:14 PM
>>> >> To: [EMAIL PROTECTED]
>>> >> Subject: Re: HBase roadmaps
>>> >>
>>> >> I didn't know this view existed in jira. Nice.
>>> >>
>>> >> I think we can drop 0.20.7. Would anyone recommend its use?
>>> >>
>>> >>     - Andy
>>> >>
>>> >>
>>> >> > From: Stack <[EMAIL PROTECTED]>
>>> >> > Subject: Re: HBase roadmaps
>>> >> > To: [EMAIL PROTECTED]
>>> >> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>>> >> > description.  RoadMap looks like this now:
>>> >> >
>>> >> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
>>> .
>>> >> > plugin.system.project:roadmap-panel
>>> >> >
>>> >> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>>> >> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>>> >>
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>
>

So, add a tag VERSION_fundamental?  E.g. 0.92_fundamental ?
St.Ack

On Fri, Jan 21, 2011 at 8:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
> I was assuming it is not easy - a lot of stuff on JIRA is somewhat
> convoluted. But I like the tag idea to flag major work, i.e. that
> would be compiled in JIRA or externally to build the list for the top
> level roadmap.
>
> On Fri, Jan 21, 2011 at 3:43 PM, Stack <[EMAIL PROTECTED]> wrote:
>> I like Ted's suggestion.  We could add a tag for
>> "release-wont-happen-w/o-this-fix" and then make custom report.  Ain't
>> sure how to make that happen under the roadmap tag in JIRA though.
>>
>> I'll drop 0.20.7.  I too don't see any of us pushing it out.  I'll
>> weed 0.90.1 a bit too (add stuff back in if I eject something that
>> should be kept in).
>>
>> St.Ack
>>
>> On Fri, Jan 21, 2011 at 7:30 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
>>> It is possible to do (but a pain) by setting up the smaller tasks as
>>> sub-tasks on major bugs and then only setting the version for the major
>>> bugs.
>>>
>>> I don't like doing that so much since it is fairly intricate.  If you have a
>>> marker for majorness, you can probably build a custom report to do the job
>>> as well.
>>>
>>> On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>>>
>>>> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
>>>> hard to read for others. Would there be a way to use super/uber issues
>>>> for the main goals and then add the others underneath? I do not think
>>>> the priority etc. is good for that as a bug fix being a blocker rather
>>>> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
>>>> bureaucratic request and may be overkill and also not what JIRA is
>>>> for. I am just asking as it would be nice to condense fixes into the
>>>> major goals for a release.
>>>>
>>>> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
>>>> > +1 on dropping 0.20.7
>>>> >
>>>> >> -----Original Message-----
>>>> >> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>>>> >> Sent: Thursday, January 20, 2011 10:14 PM
>>>> >> To: [EMAIL PROTECTED]
>>>> >> Subject: Re: HBase roadmaps
>>>> >>
>>>> >> I didn't know this view existed in jira. Nice.
>>>> >>
>>>> >> I think we can drop 0.20.7. Would anyone recommend its use?
>>>> >>
>>>> >>     - Andy
>>>> >>
>>>> >>
>>>> >> > From: Stack <[EMAIL PROTECTED]>
>>>> >> > Subject: Re: HBase roadmaps
>>>> >> > To: [EMAIL PROTECTED]
>>>> >> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>>>> >> > description.  RoadMap looks like this now:
>>>> >> >
>>>> >> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
>>>> .
>>>> >> > plugin.system.project:roadmap-panel
>>>> >> >
>>>> >> > Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>>>> >> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >
>>>>
>>>
>>
>

Hi Stack,

That's a start. Let's try it with the CP issue and try to get a report going?

Lars

On Jan 21, 2011, at 19:07, Stack <[EMAIL PROTECTED]> wrote:

> So, add a tag VERSION_fundamental?  E.g. 0.92_fundamental ?
> St.Ack
>
> On Fri, Jan 21, 2011 at 8:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>> I was assuming it is not easy - a lot of stuff on JIRA is somewhat
>> convoluted. But I like the tag idea to flag major work, i.e. that
>> would be compiled in JIRA or externally to build the list for the top
>> level roadmap.
>>
>> On Fri, Jan 21, 2011 at 3:43 PM, Stack <[EMAIL PROTECTED]> wrote:
>>> I like Ted's suggestion.  We could add a tag for
>>> "release-wont-happen-w/o-this-fix" and then make custom report.  Ain't
>>> sure how to make that happen under the roadmap tag in JIRA though.
>>>
>>> I'll drop 0.20.7.  I too don't see any of us pushing it out.  I'll
>>> weed 0.90.1 a bit too (add stuff back in if I eject something that
>>> should be kept in).
>>>
>>> St.Ack
>>>
>>> On Fri, Jan 21, 2011 at 7:30 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
>>>> It is possible to do (but a pain) by setting up the smaller tasks as
>>>> sub-tasks on major bugs and then only setting the version for the major
>>>> bugs.
>>>>
>>>> I don't like doing that so much since it is fairly intricate.  If you have a
>>>> marker for majorness, you can probably build a custom report to do the job
>>>> as well.
>>>>
>>>> On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
>>>>> hard to read for others. Would there be a way to use super/uber issues
>>>>> for the main goals and then add the others underneath? I do not think
>>>>> the priority etc. is good for that as a bug fix being a blocker rather
>>>>> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
>>>>> bureaucratic request and may be overkill and also not what JIRA is
>>>>> for. I am just asking as it would be nice to condense fixes into the
>>>>> major goals for a release.
>>>>>
>>>>> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
>>>>>> +1 on dropping 0.20.7
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>>>>>>> Sent: Thursday, January 20, 2011 10:14 PM
>>>>>>> To: [EMAIL PROTECTED]
>>>>>>> Subject: Re: HBase roadmaps
>>>>>>>
>>>>>>> I didn't know this view existed in jira. Nice.
>>>>>>>
>>>>>>> I think we can drop 0.20.7. Would anyone recommend its use?
>>>>>>>
>>>>>>>     - Andy
>>>>>>>
>>>>>>>
>>>>>>>> From: Stack <[EMAIL PROTECTED]>
>>>>>>>> Subject: Re: HBase roadmaps
>>>>>>>> To: [EMAIL PROTECTED]
>>>>>>>> Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>>>>>>>> description.  RoadMap looks like this now:
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
>>>>> .
>>>>>>>> plugin.system.project:roadmap-panel
>>>>>>>>
>>>>>>>> Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>>>>>>>> (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>

You want to try it Lars?
St.Ack

On Sat, Jan 22, 2011 at 9:19 AM, Lars George <[EMAIL PROTECTED]> wrote:
> Hi Stack,
>
> That's a start. Let's try it with the CP issue and try to get a report going?
>
> Lars
>
> On Jan 21, 2011, at 19:07, Stack <[EMAIL PROTECTED]> wrote:
>
>> So, add a tag VERSION_fundamental?  E.g. 0.92_fundamental ?
>> St.Ack
>>
>> On Fri, Jan 21, 2011 at 8:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>>> I was assuming it is not easy - a lot of stuff on JIRA is somewhat
>>> convoluted. But I like the tag idea to flag major work, i.e. that
>>> would be compiled in JIRA or externally to build the list for the top
>>> level roadmap.
>>>
>>> On Fri, Jan 21, 2011 at 3:43 PM, Stack <[EMAIL PROTECTED]> wrote:
>>>> I like Ted's suggestion.  We could add a tag for
>>>> "release-wont-happen-w/o-this-fix" and then make custom report.  Ain't
>>>> sure how to make that happen under the roadmap tag in JIRA though.
>>>>
>>>> I'll drop 0.20.7.  I too don't see any of us pushing it out.  I'll
>>>> weed 0.90.1 a bit too (add stuff back in if I eject something that
>>>> should be kept in).
>>>>
>>>> St.Ack
>>>>
>>>> On Fri, Jan 21, 2011 at 7:30 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
>>>>> It is possible to do (but a pain) by setting up the smaller tasks as
>>>>> sub-tasks on major bugs and then only setting the version for the major
>>>>> bugs.
>>>>>
>>>>> I don't like doing that so much since it is fairly intricate.  If you have a
>>>>> marker for majorness, you can probably build a custom report to do the job
>>>>> as well.
>>>>>
>>>>> On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> +1 on dropping and I like the JIRA based roadmap, but it is somewhat
>>>>>> hard to read for others. Would there be a way to use super/uber issues
>>>>>> for the main goals and then add the others underneath? I do not think
>>>>>> the priority etc. is good for that as a bug fix being a blocker rather
>>>>>> falls under a "Misc Stability Fixes" etc. I know, sounds like a purely
>>>>>> bureaucratic request and may be overkill and also not what JIRA is
>>>>>> for. I am just asking as it would be nice to condense fixes into the
>>>>>> major goals for a release.
>>>>>>
>>>>>> On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[EMAIL PROTECTED]> wrote:
>>>>>>> +1 on dropping 0.20.7
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Andrew Purtell [mailto:[EMAIL PROTECTED]]
>>>>>>>> Sent: Thursday, January 20, 2011 10:14 PM
>>>>>>>> To: [EMAIL PROTECTED]
>>>>>>>> Subject: Re: HBase roadmaps
>>>>>>>>
>>>>>>>> I didn't know this view existed in jira. Nice.
>>>>>>>>
>>>>>>>> I think we can drop 0.20.7. Would anyone recommend its use?
>>>>>>>>
>>>>>>>>     - Andy
>>>>>>>>
>>>>>>>>
>>>>>>>>> From: Stack <[EMAIL PROTECTED]>
>>>>>>>>> Subject: Re: HBase roadmaps
>>>>>>>>> To: [EMAIL PROTECTED]
>>>>>>>>> Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92
>>>>>>>>> description.  RoadMap looks like this now:
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira
>>>>>> .
>>>>>>>>> plugin.system.project:roadmap-panel
>>>>>>>>>
>>>>>>>>> Its showing 0.20.7, then 0.90.1, then 0.92.0.  You think that right?
>>>>>>>>> (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>