Hello,
We are testing Gen3 and I am using the docker-compose method to stand up a test environment. All services have come up with the exception of guppy, data-portal and nginx. I am seeing the following in the docker logs for guppy:
..snip..
"indices": [
{
"index": "etl",
"type": "case"
},
{
"index": "file",
"type": "file"
}
],
"configIndex": "etl_array-config",
"authFilterField": "auth_resource_path",
"aggregationIncludeMissingData": true,
"missingDataAlias": "no data"
},
"port": 80,
"path": "/graphql",
"arboristEndpoint": "http://arborist-service",
"tierAccessLevel": "private",
"tierAccessLimit": 1000,
"logLevel": "INFO",
"enableEncryptWhiteList": false,
"encryptWhitelist": [],
"analyzedTextFieldSuffix": ".analyzed",
"matchedTextHighlightTagName": "em",
"allowedMinimumSearchLen": 2
}
[05:03:01] INFO: [ES.initialize] getting mapping from elasticsearch...
(node:7) UnhandledPromiseRejectionWarning: Error: [ES.initialize] error getting mapping from ES index "file": index_not_found_exception
at client.indices.getMapping.then.err (/guppy/dist/server/es/index.js:171:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:7) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[05:03:01] INFO: [ES] connected to elasticsearch at http://esproxy-service:9200.
Am I supposed to create these Index's manually? If so, what is the correct way to do this?
Thanks,
-J