clarencen/lshift — Issue #257: CategoryDescriptors should be strongly typed
Author: clarencen
Created: 2011-11-14 22:42:17+00:00
State: open

Currently, bounded range CategoryDescriptors initialize themselves to be a typeless RangeCategoryConstraint. This causes an issue when a default bound is set in the config, e.g.:

@@@

@@@

This results in the following type error:

@@@
15:33:41.940 [akka:event-driven:dispatcher:global-10] ERROR PairActor:82 - FAILED to synchronise pair Staging7
scala.MatchError: RangeQueryConstraint(bizDate,2011-01-01,2011-01-31)
at net.lshift.diffa.kernel.indexing.LuceneVersionCorrelationStore$$anonfun$applyConstraints$1.apply(LuceneVersionCorrelationStore.scala:112) ~[diffa-kernel-0.9.3-SNAPSHOT.jar:na]
@@@

What should probably happen here is that type information in the XML is used to create a more appropriately typed RangeQueryConstraint.