Configurable granularity for range descriptors
Reported by Ben Hood | August 15th, 2011 @ 07:37 PM
Although this feature should not be encouraged, it should be possible to set a maximum descriptor granularity that can override the default granularity applied to a descriptor by its data type. This allows the agent to descend from a specified level of coarseness in the initial query it sends to a participant.
The config element should look like this:
<range-category name="bizDate" data-type="date" lower="1888" upper="1889" max-granularity="individual"/>
Comments and changes to this ticket
-
Ben Hood August 15th, 2011 @ 07:37 PM
- Assigned user set to “Ben Hood”
- State changed from “new” to “open”
- Milestone cleared.
- Milestone order changed from “113” to “0”
-
Ben Hood August 15th, 2011 @ 07:39 PM
(from [aea7743217f25127eef66a39a022d6e92e94fcb6]) [#343] Initial change to config file https://github.com/lshift/diffa/commit/aea7743217f25127eef66a39a022...
-
Ben Hood August 15th, 2011 @ 07:41 PM
It is with regret that I have to push this patch further up the stack than the persistent-diffs branch, because #294 contains the refactored Hibernate migrations :-(
-
Ben Hood August 15th, 2011 @ 07:43 PM
(from [a0e35af0ecc536c675e6c26ff6d7fc78c41a2b6e]) [#343] Forgot to stage this Db file https://github.com/lshift/diffa/commit/a0e35af0ecc536c675e6c26ff6d7...
-
Ben Hood August 15th, 2011 @ 07:57 PM
(from [6f00a55786a32946409d01c746c71915543db9d0]) [#343] Added a test to check the granularity override https://github.com/lshift/diffa/commit/6f00a55786a32946409d01c746c7...
-
-
-
Ben Hood August 15th, 2011 @ 08:14 PM
- State changed from “open” to “resolved”
PR raised for this - I'll take the hit for merging this into the persistent-diffs branch.
-
Paul Jones August 15th, 2011 @ 09:28 PM
- State changed from “resolved” to “open”
Only issue was the incorrect schema version in the v4 file, so as long as fixing that doesn't cause any issues, then it looks good.
-
Ben Hood August 16th, 2011 @ 12:56 AM
(from [0d2356ca8796897b63019953c0b2d20f5373b654]) [#343] DB version should be 4, not 3 https://github.com/lshift/diffa/commit/0d2356ca8796897b63019953c0b2...
-
Ben Hood August 16th, 2011 @ 01:06 AM
- State changed from “open” to “resolved”
- Assigned user changed from “Ben Hood” to “Paul Jones”
Addressed QA remark
-
-
Paul Jones August 16th, 2011 @ 08:12 AM
- State changed from “resolved” to “closed”
QA+
On a side note, should we raise a follow up bug to propogate this into set constraints too?
-
Ben Hood August 16th, 2011 @ 08:22 AM
I'm not sure that I follow - are you suggesting that granularity get
wired into set constraints? -
Paul Jones August 16th, 2011 @ 08:31 AM
Not quite. Set constraints currently always get sent out individually, which was a change we made from the original behaviour of sending all possible values in the first request, and then sending them individually upon discrepancies being detected. Given we now configure the granularity of range constraints, we could configure set constraints max-granularity as either "batch" or "individual".
-
Ben Hood August 16th, 2011 @ 08:33 AM
(from [d68a007a56cfb0c9a3c8f45418be9be61fe82a55]) Merge [#343] into persistent-diffs https://github.com/lshift/diffa/commit/d68a007a56cfb0c9a3c8f45418be...
-
Ben Hood August 16th, 2011 @ 06:59 PM
- Title changed from “Set descriptor granularity in config” to “Configurable granularity for range descriptors”
-
Ben Hood August 16th, 2011 @ 07:02 PM
OK, cool, I take your point about the set constraints - see #345 for a follow up.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood