This is an automated email from the ASF dual-hosted git repository.
jsinovassinnaik pushed a change to branch UNOMI-817-copy
in repository https://gitbox.apache.org/repos/asf/unomi.git
discard aa78e9215 tmp
discard a95a337f6 simplify query
omit 1d70bc2f0 change the way the profile are updated
omit 81f2f84a9 refacto condition builder
omit aa76073de add test
omit 425e617b8 feedback
omit 2e1389bc1 fix tests
omit c92bc9755 UNOMI-817: transform pastEvents to nested property
omit d4bb0488c UNOMI-817: set pastEvents as flattened and clean existing
mapping
add a1c4f774b UNOMI-817: set pastEvents as nested and clean existing
mapping (#659)
add dbd2da9f4 tmp
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (aa78e9215)
\
N -- N -- N refs/heads/UNOMI-817-copy (dbd2da9f4)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../unomi/plugins/baseplugin/actions/SetEventOccurenceCountAction.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
