Strongloop Loopback connector for Elasticsearch
npm-shrinkwrap.json file from a previous working deployment to help make sure that context+CLS continue to behave predictably and don't fail all of a sudden because of unfrozen dependency or sub-sub-sub dependency changes
https://gitter.im/strongloop/loopback room
for your benefit here is cutout from my own research (again nothing to do with ES connector):
With that in mind, what's Loopback's plan here? This seems like a major pain point for the framework. The Loopback Context is currently dangerously unreliable, and moving away from CLS would be a huge undertaking. However, not having a good way to pass state becomes a huge problem at times. We can explicitly pass things via options in a lot of cases, but it's not universal and it doesn't cover built-ins.
What's the plan?
https://github.com/strongloop/loopback/issues/1676#issuecomment-241665300
https://gitter.im/strongloop/loopback room will give you better answers than me
native query ... I am not sure if that means that score will come across, just that we can search in ES DSL ... I could be wrong ... Other comments by folks can be useful
I'm new to elasticsearch and the loopback connector. I've downloaded the sample and followed the instructions https://github.com/strongloop-community/loopback-connector-elastic-search. Guidance suggests to use localhost:3000/explorer once setup complete. It seems all the operations in the explorer respond with an error. Any suggestions?
"name": "Error",
"status": 401,
"message": "Authorization Required"
re-reading what i typed, it sounds defensive of me but that wasn't my intention ... please read the following for the content and not the tone :)
@lukewendling - not sure what native support for scrolling means from person to person ... for example, the underlying client is provided by ES so yes there is native support for scrolling because that client has it ... but if that means: Is scrolling used to deliver/manage any and all results everywhere by the ESConnector as a best practice? then no! Some amount of thought would be required to identify the places in code where it makes sense ... as simple as it might seem to others, sharing usecases with me helps me do better.
Now I did use scrolling for deletion ... if you happen to be using 2.x as your ES ... you can find more about the usecase that was shared with me and how i went down that rabbit hole to come up with a solution here: strongloop-community/loopback-connector-elastic-search#45
Maybe the commits from there can inspire a solution or a request for enhancement?
https://www.npmjs.com/package/loopback-connector-es
Hi,
we are developing a profile database for medical experts and i'm in the process of figuring out if the es-connector is suitable for our setup.
We already have a loopback api backed by a mongodb. In this db we are storing profiles consisting of different model documents and their relations.
Now we wanne make the profiles together w/ some computed values accessible via eleasticsearch. Our approach is to generate single profile documents w/ all searchable fields, including the computed ones and put them initially and on update via rest calls into elasticsearch.
We want to use elasticsearch because of speed, the highlighting support and relevance search.
Now my questions are:
- What can be the purpose of the es-connector in this setup? An unified api?
- Do we have then to use the loopback query syntax or the elasticsearch query syntax?
- Can we still use highlighting and relevance search?
Thanks a lot
Thomas
"mappings": [
{
"name": "contactsearch",
"index": "hero-search",
"type":"contact",
"properties": {
"name": {"type": "string"},
"skills": {"type": "string"},
"categories":{"type": "string"},
"categoryIds":{"type": "string"},
"email": {"type": "string", "analyzer": "email"},
"phone": {"type": "string"}
}
}],
"settings": {
"analysis": {
"filter": {
"email": {
"type": "pattern_capture",
"preserve_original": 1,
"patterns": [
"([^@]+)",
"(\\p{L}+)",
"(\\d+)",
"@(.+)",
"([^-@]+)"
]
}
},
"analyzer": {
"email": {
"tokenizer": "uax_url_email",
"filter": [
"email",
"lowercase",
"unique"
]
}
}
}
}
@nejczupan
hey guys, I have a quick question.
I have daily indices.
I am reindexing and I would like to have a simple template which creates indicies with setting I like.
Then I use static mapping with dynamic strict.
The problem is that the next day (due to daily indices) my static mapping is not being used but rather it uses default template without static mapping used previous day.
What would be my solution?
so i would have to say:
no @Alejandro_ST_17_twitter its not possible to perform ELS aggregations using this connector
there is no good out-of-the-box support for this ... its not impossible with some thought and vision but i cannot imagine what method name i should expose such support under and what all might be useful for different folks :(
