decrease earliest epoch value of query xml by 3 hours query XML - #415
decrease earliest epoch value of query xml by 3 hours query XML#415elliVM wants to merge 11 commits into
Conversation
|
please rebase |
1551c09 to
bfeceed
Compare
|
Rebased |
|
I think you also need to change it for the produced XML and spark column to have an effect |
eemhu
left a comment
There was a problem hiding this comment.
LGTM, but should EqualsVerifier be added to pth-10 as well for hashCode tests?
yes, please add @elliVM |
|
Added EqualsVerifier library and contract test. |
94ee229 to
351832d
Compare
|
Rebased and duplicate dependency removed |
| ); | ||
| final ElementNode returnValue; | ||
| if (timeQualifier.isStartTime()) { | ||
| final long decreaseValue = 3 * 60 * 60 * 1000; // decrease 3 hours from earliest |
There was a problem hiding this comment.
please make this configurable:
dpl.pth_10.logicalstatement.TimeStatement.xmlDecreaseStartTime=true
check that all paths parts to the key are defined as this is an optional key i.e.
hasKey(dpl.pth_10.logicalstatement) && hasKey(dpl.pth_10.logicalstatement.TimeStatement) && hasKey(dpl.pth_10.logicalstatement.TimeStatement.xmlDecreaseStartTime)
ccc94ba to
2319474
Compare
|
rebased and update code, further changes required after #572 |
…dd EqualsVerifier and contract test
d509b51 to
5037b98
Compare
Workaround to decrease earliest epoch value given to query XML by 3 hours to work with pth_06 that uses helsinki timezone.