[jira] [Commented] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
[ https://issues.apache.org/jira/browse/HBASE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459408#comment-13459408 ] Lukas commented on HBASE-6806: -- python, c++ and java: worksforme™ I had no chance to test php, perl and ruby, they might even have syntactic errors in it... > HBASE-4658 breaks backward compatibility / example scripts > -- > > Key: HBASE-6806 > URL: https://issues.apache.org/jira/browse/HBASE-6806 > Project: HBase > Issue Type: Bug > Components: thrift >Affects Versions: 0.94.0 >Reporter: Lukas > Attachments: HBASE-6806-fix-examples.diff > > > HBASE-4658 introduces the new 'attributes' argument as a non optional > parameter. This is not backward compatible and also breaks the code in the > example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
[ https://issues.apache.org/jira/browse/HBASE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas updated HBASE-6806: - Attachment: HBASE-6806-fix-examples.diff corrected patch name. > HBASE-4658 breaks backward compatibility / example scripts > -- > > Key: HBASE-6806 > URL: https://issues.apache.org/jira/browse/HBASE-6806 > Project: HBase > Issue Type: Bug > Components: thrift >Affects Versions: 0.94.0 >Reporter: Lukas > Attachments: HBASE-6806-fix-examples.diff > > > HBASE-4658 introduces the new 'attributes' argument as a non optional > parameter. This is not backward compatible and also breaks the code in the > example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
[ https://issues.apache.org/jira/browse/HBASE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas updated HBASE-6806: - Attachment: HBASE-4658-fix-examples.diff Adding patch for fixing DemoClient.*. Tested: python, cpp, java Untested: php, perl, ruby Also refactored the python example to match the cpp and java version. > HBASE-4658 breaks backward compatibility / example scripts > -- > > Key: HBASE-6806 > URL: https://issues.apache.org/jira/browse/HBASE-6806 > Project: HBase > Issue Type: Bug > Components: thrift >Affects Versions: 0.94.0 >Reporter: Lukas > > HBASE-4658 introduces the new 'attributes' argument as a non optional > parameter. This is not backward compatible and also breaks the code in the > example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
[ https://issues.apache.org/jira/browse/HBASE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas updated HBASE-6806: - Attachment: (was: HBASE-4658-fix-examples.diff) > HBASE-4658 breaks backward compatibility / example scripts > -- > > Key: HBASE-6806 > URL: https://issues.apache.org/jira/browse/HBASE-6806 > Project: HBase > Issue Type: Bug > Components: thrift >Affects Versions: 0.94.0 >Reporter: Lukas > > HBASE-4658 introduces the new 'attributes' argument as a non optional > parameter. This is not backward compatible and also breaks the code in the > example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
[ https://issues.apache.org/jira/browse/HBASE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457862#comment-13457862 ] Lukas commented on HBASE-6806: -- i see, thrift does not support optional function arguments. maybe fix the examples then. > HBASE-4658 breaks backward compatibility / example scripts > -- > > Key: HBASE-6806 > URL: https://issues.apache.org/jira/browse/HBASE-6806 > Project: HBase > Issue Type: Bug > Components: thrift >Affects Versions: 0.94.0 >Reporter: Lukas > > HBASE-4658 introduces the new 'attributes' argument as a non optional > parameter. This is not backward compatible and also breaks the code in the > example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6806) HBASE-4658 breaks backward compatibility / example scripts
Lukas created HBASE-6806: Summary: HBASE-4658 breaks backward compatibility / example scripts Key: HBASE-6806 URL: https://issues.apache.org/jira/browse/HBASE-6806 Project: HBase Issue Type: Bug Components: thrift Affects Versions: 0.94.0 Reporter: Lukas HBASE-4658 introduces the new 'attributes' argument as a non optional parameter. This is not backward compatible and also breaks the code in the example section. Resolution: Mark as 'optional' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4658) Put attributes are not exposed via the ThriftServer
[ https://issues.apache.org/jira/browse/HBASE-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457802#comment-13457802 ] Lukas commented on HBASE-4658: -- i go and buy an 'optional'. > Put attributes are not exposed via the ThriftServer > --- > > Key: HBASE-4658 > URL: https://issues.apache.org/jira/browse/HBASE-4658 > Project: HBase > Issue Type: Bug > Components: thrift >Reporter: dhruba borthakur >Assignee: dhruba borthakur > Fix For: 0.94.0 > > Attachments: ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, ThriftPutAttributes1.txt > > > The Put api also takes in a bunch of arbitrary attributes that an application > can use to associate metadata with each put operation. This is not exposed > via Thrift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4658) Put attributes are not exposed via the ThriftServer
[ https://issues.apache.org/jira/browse/HBASE-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457800#comment-13457800 ] Lukas commented on HBASE-4658: -- Making the 'attributes' argument would have been better. This breaks the thrift examples and also backward compatibility > Put attributes are not exposed via the ThriftServer > --- > > Key: HBASE-4658 > URL: https://issues.apache.org/jira/browse/HBASE-4658 > Project: HBase > Issue Type: Bug > Components: thrift >Reporter: dhruba borthakur >Assignee: dhruba borthakur > Fix For: 0.94.0 > > Attachments: ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.1.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.2.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, > ASF.LICENSE.NOT.GRANTED--D1563.3.patch, ThriftPutAttributes1.txt > > > The Put api also takes in a bunch of arbitrary attributes that an application > can use to associate metadata with each put operation. This is not exposed > via Thrift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1212) merge tool expects regions all have different sequence ids
[ https://issues.apache.org/jira/browse/HBASE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290022#comment-13290022 ] Lukas commented on HBASE-1212: -- Can someone comment, if this is still an issue? > merge tool expects regions all have different sequence ids > -- > > Key: HBASE-1212 > URL: https://issues.apache.org/jira/browse/HBASE-1212 > Project: HBase > Issue Type: Bug >Reporter: stack > > Currently merging two regions, the merge tool will compare their sequence > ids. If same, it will decrement one. It needs to do this because on region > open, files are keyed by their sequenceid; if two the same, one will erase > the other. > Well, with the move to the aggregating hfile format, the sequenceid is > written when the file is created and its no longer written into an aside file > but as metadata on to the end of the file. Changing the sequenceid is no > longer an option. > This issue is about figuring a solution for the rare case where two store > files have same sequence id AND we want to merge the two regions. -- 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
[jira] [Created] (HBASE-3783) hbase-0.90.2.jar exists in hbase root and in 'lib/'
hbase-0.90.2.jar exists in hbase root and in 'lib/' --- Key: HBASE-3783 URL: https://issues.apache.org/jira/browse/HBASE-3783 Project: HBase Issue Type: Bug Components: build Affects Versions: 0.90.2 Reporter: Lukas Priority: Minor The official HBase 0.90.2 release contains a hbase-0.90.2.jar in'' and in '/lib/'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-1212) merge tool expects regions all have different sequence ids
[
https://issues.apache.org/jira/browse/HBASE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001467#comment-13001467
]
Lukas commented on HBASE-1212:
--
Hi there,
When using util.merge on a table (created under hbase 0.20.6, but now running
under 0.90.1) I get the following exception very often (which I think is the
result of this jira):
{code}
FATAL util.Merge: Merge failed
java.io.IOException: Files have same sequenceid: 1283640296746
at org.apache.hadoop.hbase.regionserver.HRegion.merge(HRegion.java:2785)
at org.apache.hadoop.hbase.util.Merge.merge(Merge.java:287)
at org.apache.hadoop.hbase.util.Merge.mergeTwoRegions(Merge.java:238)
at org.apache.hadoop.hbase.util.Merge.run(Merge.java:110)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at org.apache.hadoop.hbase.util.Merge.main(Merge.java:379)
{code}
Unfortunately at this point some families of the region were already moved to
the new merged region which leaves the table in an inconsistent state.
Is there any way to detect this failure case before running the merge tool
(except for opening the store files in advance and calling getMaxSequenceId)?
Same issue is also mentioned in the
[comments|https://issues.apache.org/jira/browse/HBASE-1621?focusedCommentId=12993477#comment-12993477]
of HBASE-1621
> merge tool expects regions all have different sequence ids
> --
>
> Key: HBASE-1212
> URL: https://issues.apache.org/jira/browse/HBASE-1212
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>
> Currently merging two regions, the merge tool will compare their sequence
> ids. If same, it will decrement one. It needs to do this because on region
> open, files are keyed by their sequenceid; if two the same, one will erase
> the other.
> Well, with the move to the aggregating hfile format, the sequenceid is
> written when the file is created and its no longer written into an aside file
> but as metadata on to the end of the file. Changing the sequenceid is no
> longer an option.
> This issue is about figuring a solution for the rare case where two store
> files have same sequence id AND we want to merge the two regions.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
