compatibility changes for cassandra 1.0.7, DatumType comparator now in reverse
compatibility changes for cassandra 1.0.7, DatumType now in reverse
forgot to mark two test methods with @Test
created new GoogleContactsDatumType comparator
modified test to use combined name rather than last name~first name
now does a case-insensitive compare
fall back to document id if name/email is the same
Modified to use staticly compiled Pattern objects for matches and split. All existing tests pass
added readme
Merge pull request #1 from TheLastPickle/comparator-update-TLP

Comparator update tlp
update cass version
Revert "Merge pull request #1 from TheLastPickle/comparator-update-TLP"

This reverts commit 4d2a1217f67c0ef4dd4bf403416cf854b41f072b, reversing
changes made to 6503779eb250bb306f38c87f55b9fd5f1f7b9f89.

Conflicts:

	build.xml
Revert "Revert "Merge pull request #1 from TheLastPickle/comparator-update-TLP""

This reverts commit aab6e53c53596faae1ef529dbcd26967256d309c.
update to reflect what is actually in production and cassandra 1.2.5
use static regexes
removed a matcher allocation in favor of reset, changed BigInteger compare to Long, falling back to BigInteger if we get a number format exception
add ThreadLocal storage for the Matchers

ThreadLocal storage to reduce allocations. Also copied the code for split()
from Pattern to avoid allocating the Matcher.
Merge pull request #5 from TheLastPickle/2nd-pass-TLP

removed a matcher allocation in favor of reset, changed BigInteger compa...