[Unomi-485] invalid comparison operator https://issues.apache.org/jira/browse/UNOMI-485#310
Closed
sagyr wants to merge 136 commits intoapache:masterfrom
Closed
[Unomi-485] invalid comparison operator https://issues.apache.org/jira/browse/UNOMI-485#310sagyr wants to merge 136 commits intoapache:masterfrom
sagyr wants to merge 136 commits intoapache:masterfrom
Conversation
(cherry picked from commit bce962e)
- Add new profile to easily deactivate integration and performance tests - Add SHA512 checksum generation for package (cherry picked from commit 0b96154)
- Add & fix sample that was not included in the build. (cherry picked from commit da76c72)
…d MVEL2 scripting languages (apache#158) * Make it possible to white list and black list classes used in OGNL and MVEL2 scripting languages * Add new integration test to AllITs list * Add some documentation for the configuration parameters (cherry picked from commit 789ae8e)
# Conflicts: # .travis.yml # buildAndDeployUnomiFromTag.sh
* fix(SetEventOccurenceCountAction.java) - check the event's timestamp before increase the pastEvent counter by 1 * fix(SetEventOccurenceCountAction.java) - change comment to Serge suggestion * rename(UpdateEventFromContextServletIT) - rename test class to "ContextServletIT" * improve(ContextServletIT) - refactor existing tests * improve(ContextServletIT) - delete indexes' CONTENT instead of deleting the indexes * feat(ContextServletIT) - remove sessions between tests * improve(TestUtils) - change "executeContextJSONRequest" function to static * feat(ContextServletIT) - add unit-tests for past-event-segment calculation when adding events with custom timestamp Co-authored-by: nlevitsky <Pitzek1305>
remove tag reset
Update travis
…rofile as master when flagged (#89)
…ofile properties (#90)
This reverts commit 6585517.
…n value does not exist (#108)
Update segments in profile - via elastic query & script retry update when failure occurs Added feature flag
fix persistence service documentation Optimizations ES: Add/remove to list script moved to es persistence service Update by query: configurable slices & batch size Exec list property update via script Add configurable slices amount for elastic service Removed unused props
…ould return true like elastic evaluator (#117)
…onOperator is unrecognized
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Title format:
Please add a meaningful description for your change here
When building a property condition query, throw exception if comparisonOperator is unrecognised.
https://issues.apache.org/jira/browse/UNOMI-485
Please following this checklist to help us incorporate your contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
[UNOMI-XXX] - Title of the pull requestsignificant new parts of code.
Copy the description to the related JIRA issue
mvn clean install -P integration-teststo make sure basic checks pass. A more thorough check will beperformed on your pull request automatically.
Trivial changes like typos do not require a JIRA issue (javadoc, project build changes, small doc changes, comments...).
If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.