[ 
https://issues.apache.org/jira/browse/FLUME-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274835#comment-13274835
 ] 

[email protected] commented on FLUME-1183:
------------------------------------------------------



bq.  On 2012-05-14 10:20:20, Juhani Connolly wrote:
bq.  > 
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/HBaseSink.java,
 line 152
bq.  > <https://reviews.apache.org/r/5073/diff/4/?file=108798#file108798line152>
bq.  >
bq.  >     I'm not entirely convinced by the need to set all puts to the same 
column family, when everything else is pretty customizable. Saving on 
transferring the columnFamily data everytime? Perhaps make it overridable with 
an optional header.

I am going to file a bug for this, and for adding unit tests.


bq.  On 2012-05-14 10:20:20, Juhani Connolly wrote:
bq.  > 
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/HBaseSink.java,
 line 175
bq.  > <https://reviews.apache.org/r/5073/diff/4/?file=108798#file108798line175>
bq.  >
bq.  >     Looks to me like if there is no configuration for this in the 
context, you'll be passing a null here... Which will then result in a NPE?

fixed.


bq.  On 2012-05-14 10:20:20, Juhani Connolly wrote:
bq.  > 
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/HBaseSink.java,
 line 203
bq.  > <https://reviews.apache.org/r/5073/diff/4/?file=108798#file108798line203>
bq.  >
bq.  >     I think you should be calling putEventsAndCommit here? Otherwise it 
looks to me like you're losing anything that was take'd between the last PEAC 
and reaching the batchsize

Fixed.


- Hari


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5073/#review7835
-----------------------------------------------------------


On 2012-05-14 18:31:15, Hari Shreedharan wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/5073/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-05-14 18:31:15)
bq.  
bq.  
bq.  Review request for Flume.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Hbase sink.
bq.  
bq.  
bq.  This addresses bug FLUME-1183.
bq.      https://issues.apache.org/jira/browse/FLUME-1183
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    bin/flume-ng 0108997 
bq.    flume-ng-dist/pom.xml 5bdcfe7 
bq.    flume-ng-sinks/flume-ng-hbase-sink/pom.xml PRE-CREATION 
bq.    
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/HBaseSink.java
 PRE-CREATION 
bq.    
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/HbaseEventSerializer.java
 PRE-CREATION 
bq.    
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/SimpleHbaseEventSerializer.java
 PRE-CREATION 
bq.    
flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/SimpleRowKeyGenerator.java
 PRE-CREATION 
bq.    
flume-ng-sinks/flume-ng-hbase-sink/src/test/java/org/apache/flume/sink/hbase/TestHBaseSink.java
 PRE-CREATION 
bq.    flume-ng-sinks/pom.xml acb3087 
bq.    pom.xml 8c11a2d 
bq.  
bq.  Diff: https://reviews.apache.org/r/5073/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Unit tests added
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Hari
bq.  
bq.


                
> Implement an HBase Sink which supports table level access
> ---------------------------------------------------------
>
>                 Key: FLUME-1183
>                 URL: https://issues.apache.org/jira/browse/FLUME-1183
>             Project: Flume
>          Issue Type: New Feature
>          Components: Sinks+Sources
>    Affects Versions: v1.2.0
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>             Fix For: v1.2.0
>
>
> This is what I intend to do:
> * Insert the row key from event headers. Pick the column family and column 
> from configuration, not from headers. 
> * Allow configuration to specify default for row key. If no row key exists in 
> header, then take the default value from the configuration. I don't want to 
> dump everything into the table with the same row key. 
> * I don't intend to support multiple tables, column families or columns in 
> the same sink. We can use multiplexing channel selector to use different 
> sinks for different tables/columns.
> I know the existence of another jira for porting the HBase sink from OG, but 
> didn't see any activity for a while on that. 

--
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

        

Reply via email to