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

ElasticSearch index activation #373

Open
namebrandon opened this issue Mar 19, 2018 · 4 comments
Open

ElasticSearch index activation #373

namebrandon opened this issue Mar 19, 2018 · 4 comments

Comments

@namebrandon
Copy link

namebrandon commented Mar 19, 2018

The following is the response from every Curl call to ES.. It appears that this is an ES issue?

This is output from my local machine (OSX) curling to the Herd instance created by CloudFormation (artifact jar 0.65).


 curl -X POST \
>   --header 'Content-Type: application/json' \
>   --header 'Accept: application/json' \
>   -d '{"searchIndexType": "BUS_OBJCT_DFNTN"}' \
>   http://myip:8080/herd-app/rest/searchIndexes

{"statusCode":400,"statusDescription":"Bad Request","message":"unable to detect content type from source []","messageDetails":[]}

I have tried the same from Postman and see the same response.

@DavidBalash
Copy link
Member

DavidBalash commented Mar 19, 2018

I have added some more information to the Elasticsearch setup page on the herd wiki: https://github.com/FINRAOS/herd/wiki/Elasticsearch-setup and the information provided may help in solving your issue. Summary below:

We are currently using Elasticsearch version 5.1.1, please make sure that is the version that you have installed. This version number corresponds to the org.elasticsearch dependency artifact and the JEST client dependency artifact that the herd code uses to connect to Elasticsearch. Elasticsearch version 5.2 and later contains breaking changes https://www.elastic.co/guide/en/elasticsearch/reference/5.5/release-notes-5.2.0.html.

Important: Please install an Elasticsearch software version corresponding to the Elasticsearch library version in the Herd pom.xml file.
The version number can be found in the <elasticsearch.version> property in the top level pom.xml (https://github.com/FINRAOS/herd/blob/master/pom.xml)
file in the herd repository.

Also make sure that the configuration values elasticsearch.bdef.mappings.json, elasticsearch.bdef.settings.json, elasticsearch.tag.mappings.json, and elasticsearch.tag.settings.json are set as CLOB values in the configuration table (cnfgn), cnfgn_value_cl column.

@namebrandon
Copy link
Author

Thanks, David! I'm just using the out of the box CloudFormation template, not sure if there's an ability to control the ES version? I think Nate had mentioned this was being updated, with some more changes to come.

@DavidBalash
Copy link
Member

The CloadFormation template does a yum install of ES version 5.x, which ends up installing ES 5.6.8. We will need to update the CF template so that it installs 5.1.1. For now as a work around, you could login to the EC2 instance and re-install ES under /usr/share/elasticsearch/, or modify the CF template and rebuild the stack.

@dmoore247
Copy link

The 0.68 version of the CloudFormation template installs the correct version of the Elastic Search (5.1.1), and it creates the two indexes bdef_###### and tag_##### however it fails to activate those indexes within Herd.
The Elastic Search Setup page shows how to activate the indexes. To discover the existing indexes. this command is valuable:
curl --header 'Accept: application/json' -X GET http://localhost:8080/herd-app/rest/searchIndexes |jq
Once this was done, I was able to navigate the UI rather successfully.

FINRAOSS pushed a commit that referenced this issue Aug 24, 2018
* commit '4ef9f9688175b8af0fd72dc145f72fe9aa5d752d':
  DM-10884: Search by BData Attributes rapidly and efficiently
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

No branches or pull requests

3 participants