Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elastic 5.4 #21

Open
wants to merge 58 commits into
base: master
Choose a base branch
from
Open

Elastic 5.4 #21

wants to merge 58 commits into from

Conversation

shroffk
Copy link
Contributor

@shroffk shroffk commented Oct 25, 2017

No description provided.

Eric Berryman and others added 22 commits May 22, 2017 12:13
* commit '771ecd1f0412b504cb2ea992f76a9fae6ffe612e': (26 commits)
  moved debian package to use payara and systemd
  shorter wait for payara startup
  running tests from payara micro
  asadmin commands for integration tests
  updated scripts to use lambdas, and fixed the document missing tests to match the new output
  updating scripts
  updating to new script api
  remove script from TagsResource
  add exceptions to cover non existing channel for property resource
  refresh only on bulk requests, change property put to use XContentBuilder, instead of script
  travis: remove debug
  removing nosetests arg causing issue on travis
  travis: add debug mvn
  travis: use addon to install python-nose
  added base.dir to relative path in pom.xml
  updated mapping_definitions to use text/keyword, then sort from keyword
  travis: url change
  update travis and readme to elastic 5.4
  changed settings to api, added new depends
  fix null pointer
  ...
* commit '977e514f1cf8b12af2bf94d65ba4ffdbc80ddedc':
  fix version
  update debian packaging
* commit '61fb4397273581575fd24e25379078b52c51eb09':
  add initialized settings, not empty settings
  update mapping file for deb package
@berryma4
Copy link
Contributor

The job exceeded the maximum time limit for jobs, and has been terminated.
How do you get this to pass on TravisCI? It keeps running out of time.

@berryma4
Copy link
Contributor

Don't merge. If you even want this on master, maybe a branch is in order, and a cleaning up of the commits (squashing some).

@shroffk
Copy link
Contributor Author

shroffk commented Oct 24, 2018

we now have elastic 6

@shengb
Copy link

shengb commented Oct 24, 2018

@shroffk Does it mean with this PR #21, we can update the CF to elastic 6 now?

@shroffk
Copy link
Contributor Author

shroffk commented Oct 24, 2018

I think we might not merge this PR
Use it as a reference to update to elastic version 6

@berryma4
Copy link
Contributor

If you are interested, I'm converting this to spring boot and elastic 6.3.
(I will clean up the commits)

@shengb
Copy link

shengb commented Oct 25, 2018

I think we do need to move ahead to elastic6, and clean up the some legacies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants