You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ioannis Canellos (Updated) (JIRA)" <ji...@apache.org> on 2011/12/19 17:13:30 UTC

[jira] [Updated] (CAMEL-4743) Create a camel component for Hbase

     [ https://issues.apache.org/jira/browse/CAMEL-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos updated CAMEL-4743:
------------------------------------

    Attachment: CAMEL-4743-patch.txt

I have put together a really basic draft for the component. And since we are stilling working on releasing camel 2.9, I thought its best to add it as patch for anyone interested in having a look / providing some feedback.

The component provider a:
i) Producer: Put, Get, Delete & Scan.
ii) A consumer.
iii) An idempotent repository.

The producer can add/get multiple rows and columns by specifying them as exchange headers along with the desired operation. Operations for single row/column can also use the endpoint uri (no multiple rows/columns on the uri yet).

The results will be added as headers.

For single row/column operations values and results can be inside the body. For multiple rows/columns headers will be used instead.

For users that have needs for customizing the way that an exchange is mapped to hbase rows/columns etc, there has been added the ability to implement and use custom mappings (e.g. a user may want to use a custom objects and map its properties to columns).

Its also possible to specify custom serializers for serializing row ids/values.
                
> Create a camel component for Hbase
> ----------------------------------
>
>                 Key: CAMEL-4743
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4743
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>         Attachments: CAMEL-4743-patch.txt
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira