tree 55c3307dbdfece67ab02fcc91133d8c627437d9c
parent 44e134a9d90685b57fc60a8bcc9a8919e79e4e3b
author Keith Turner <kturner@apache.org> 1668609821 +0000
committer GitHub <noreply@github.com> 1668609821 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjdPcdCRBK7hj4Ov3rIwAAyPkIAIl9jK3V+4oIZSvB7h+a0PZA
 /sNSKPIW/A/NocD7/IIXzpTiOfgheTcqxcxLGkIPQu+RIjemHFbB2Yl6E4BgnaD3
 oLadlgiusuieKC9LBHu3xWghSo//Yp2O8/R6o0BE7UbpEti2kiDgzfP1Ji4JlhIH
 u1mgJLl98fbpfP4Z1IgGZ6A6mlFckbaz7JVIUdIvZU/hpyfymSi/YMZ0TJw8ZzHD
 6BCR2h4stqnM4+PpfIKrCxEcXYAujKzqO6V2pfHZKqZlPx6CLijO0mLr7XhedM8h
 9L5leQkKR+vLRYLhTLMEcxD8pzu9QX35wF0ri/XO73ASthdoYSIZK0oX8aeN9iM=
 =oGHb
 -----END PGP SIGNATURE-----
 

Fixes bug resolving lock w/ empty col fam. Reported in #660 (#1123)

There was a bug where if a column family was empty and the qual was not
empty this would cause lock recovery to fail.  The underlying cause was
a bug in the Column class.  This class has an isFamilySet() method that
was returning false when the family was set to the empty string.  This
cause caused lock recovery code to create an incorrect range.

The Column class was relying on internal behavior of the Bytes class
that probably changed and caused this bug.

This commit adds a new IT that recreates this bug.  If the new IT is run
w/o the fix to the Column class then it would fail as follows.

```
Running org.apache.fluo.integration.impl.FailureIT
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 8.011 sec <<< FAILURE! - in org.apache.fluo.integration.impl.FailureIT
testRecoverEmptyColumn(org.apache.fluo.integration.impl.FailureIT)  Time elapsed: 7.096 sec  <<< ERROR!
java.lang.IllegalStateException: can not abort : bob  bal  5 (UNKNOWN)
	at org.apache.fluo.integration.impl.FailureIT.testRecoverEmptyColumn(FailureIT.java:688)
```