Stack and I were chatting on IRC about settling with should get into 0.92 before pulling the trigger on the release.
Stack thinks we need online region schema editing. I agree because per-table coprocessor loading is configured via table attributes. We'd also need some kind of notification of schema update to trigger various actions in the regionserver. (For CPs, (re)load.) I'd also really like to see some form of secondary indexing. This is an important feature for HBase to have. All of our in house devs ask for this sooner or later in one form or another. Other projects have options in this arena, while HBase used to in core, but no longer. We have three people starting on this ASAP. I'd like to at least do co-design with the community. We should aim for 'simple and effective'. There are 14 blockers: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+HBASE+AND+fixVersion+%3D+%220.92.0%22+AND+resolution+%3D+Unresolved+AND+priority+%3D+Blocker Additionally, 22 marked as critical: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+HBASE+AND+fixVersion+%3D+%220.92.0%22+AND+resolution+%3D+Unresolved+AND+priority+%3D+Critical Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
