hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4605) Constraints
Date Thu, 05 Feb 2015 00:22:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306294#comment-14306294

stack commented on HBASE-4605:

This went into trunk here:

063fa64 HBASE-4605 Constraints, remove .orig files accidentally added in previous commit
5166afd HBASE-4605 Constraints (Jesse Yates)

commit 5166afddc5b93bbac5ec7f0ab4ed978471a69046
Author: Zhihong Yu <tedyu@apache.org>
Date:   Thu Dec 15 17:44:59 2011 +0000

    HBASE-4605 Constraints (Jesse Yates)

    git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1214889 13f79535-47bb-0310-9956-ffa450edef68

Looking at tags.....

2012-05-17 19:37:24 +0000  (tag: 0.94.0)
2012-05-01 23:08:25 +0000  (tag: 0.94.0RC3)
2012-05-30 17:57:29 +0000  (tag: 0.94.0mvnrelease)
2012-04-18 23:23:57 +0000  (tag: 0.94.0RC2)
2012-04-14 02:19:29 +0000  (tag: 0.94.0RC1)
2012-03-28 00:40:32 +0000  (tag: 0.94.0RC0)

... it looks like this feature made it into 0.94.

Above done for [~larsgeorge] who is trying to follow along and trying to figure when stuff
showed up (this is missing fix versions)

> Constraints
> -----------
>                 Key: HBASE-4605
>                 URL: https://issues.apache.org/jira/browse/HBASE-4605
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, Coprocessors
>    Affects Versions: 0.94.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>         Attachments: 4605-v6.txt, 4605.v7, constraint_as_cp.txt, java_Constraint_v2.patch,
java_HBASE-4605_v1.patch, java_HBASE-4605_v2.patch, java_HBASE-4605_v3.patch, java_HBASE-4605_v5.patch,
> From Jesse's comment on dev:
> {quote}
> What I would like to propose is a simple interface that people can use to implement a
'constraint' (matching the classic database definition). This would help ease of adoption
by helping HBase more easily check that box, help minimize code duplication across organizations,
and lead to easier adoption.
> Essentially, people would implement a 'Constraint' interface for checking keys before
they are put into a table. Puts that are valid get written to the table, but if not people
can will throw an exception that gets propagated back to the client explaining why the put
was invalid.
> Constraints would be set on a per-table basis and the user would be expected to ensure
the jars containing the constraint are present on the machines serving that table.
> Yes, people could roll their own mechanism for doing this via coprocessors each time,
but this would make it easier to do so, so you only have to implement a very minimal interface
and not worry about the specifics.
> {quote}

This message was sent by Atlassian JIRA

View raw message