This is an automated email from the ASF dual-hosted git repository.
shuber pushed a change to branch UNOMI-225-ES7
in repository https://gitbox.apache.org/repos/asf/unomi.git.
discard 3747fb6 ES7 support code cleanup mostly Persistence Service Impl,
removing unnecessary stuff.
discard 912d5ab UNOMI-225 ElasticSearch 7 support Model changes: - fix issue
with full text search not working
discard cd474cb fix aggregation cast issue ES7 (clean import)
discard 34a040f fix aggregation cast issue ES7
discard 4f2f357 fix scoring plan mapping creation
discard b89b9d3 adapt PropertyConditionEvaluator.getDate to Joda ES7 parser
discard 72c7a00 remove cluster health check at ES persistence service start,
as it could introduce 30sec tiemout per index when cluster is not green.
discard b55138a UNOMI-225 ElasticSearch 7 support Model changes: - bug fixes
to get queries to work properly - fixed index template setup
discard 9315ab7 UNOMI-225 ElasticSearch 7 support Model changes: - change
geonames to use context prefix (will require re-import) - added mapping types
for all types - Unomi should now start, but there are still known issues
(integration tests do not run, actions are not properly register on first
start). - index.name was changed to index.prefix
discard 98d9f06 UNOMI-225 ElasticSearch 7 support - Connection to
ElasticSearch is now working, still lots of things to fix, notably in mappings.
discard 66eb034 UNOMI-225 ElasticSearch 7 support - Connection to
ElasticSearch is not starting, but still some errors
discard d191203 UNOMI-225 ElasticSearch 7 support - Rewrote all the code in
the persistence service - Working on getting the import package statements
right, probably still some problems in them - Karaf starts but Unomi doesn't
start properly yet
discard db5a9ad WIP [UNOMI-225]
discard 2a184ae Update gitignore
discard 0fde2a8 UNOMI-225 Initial work on ElasticSearch 7 support. Includes
switching to Java High Level Rest Client This is very prelimiinary work, it
doesn't even compile yet.
add 6e75f85 Update dependencies for Karaf 4.2.x
add 0126841 Fix OSGi headers in couple of bundles. Fix bin/setenv
add f7f1b43 Downgrade to Jackson 2.9.10 (including CVE fixes) waithing
XBean fix.
add 7e077f5 Merge pull request #107 from jbonofre/KARAF42
new c0c944c UNOMI-225 Initial work on ElasticSearch 7 support. Includes
switching to Java High Level Rest Client This is very prelimiinary work, it
doesn't even compile yet.
new 87c9223 Update gitignore
new a605e27 WIP [UNOMI-225]
new 838fc1c UNOMI-225 ElasticSearch 7 support - Rewrote all the code in
the persistence service - Working on getting the import package statements
right, probably still some problems in them - Karaf starts but Unomi doesn't
start properly yet
new a9268fa UNOMI-225 ElasticSearch 7 support - Connection to
ElasticSearch is not starting, but still some errors
new 1a69880 UNOMI-225 ElasticSearch 7 support - Connection to
ElasticSearch is now working, still lots of things to fix, notably in mappings.
new 39e6070 UNOMI-225 ElasticSearch 7 support Model changes: - change
geonames to use context prefix (will require re-import) - added mapping types
for all types - Unomi should now start, but there are still known issues
(integration tests do not run, actions are not properly register on first
start). - index.name was changed to index.prefix
new 3abb04b UNOMI-225 ElasticSearch 7 support Model changes: - bug fixes
to get queries to work properly - fixed index template setup
new aa93b2e remove cluster health check at ES persistence service start,
as it could introduce 30sec tiemout per index when cluster is not green.
new 3f87ede adapt PropertyConditionEvaluator.getDate to Joda ES7 parser
new 7e5df35 fix scoring plan mapping creation
new 0f4a133 fix aggregation cast issue ES7
new 3a95b1a fix aggregation cast issue ES7 (clean import)
new 71149bc UNOMI-225 ElasticSearch 7 support Model changes: - fix issue
with full text search not working
new f694fac ES7 support code cleanup mostly Persistence Service Impl,
removing unnecessary stuff.
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 (3747fb6)
\
N -- N -- N refs/heads/UNOMI-225-ES7 (f694fac)
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.
The 15 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
package/src/main/resources/bin/setenv | 1 -
pom.xml | 17 +++++++++--------
2 files changed, 9 insertions(+), 9 deletions(-)
