by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Samuel Bednarčík
    @samuelbednarcik_twitter
    a just find out that i was using wrong version of the package, not for elasticsearch 6
    ghazaltaimur13
    @ghazaltaimur13
    hi guys, i need to send a data to two databases / data source. Is this possible? and also run migration in both the databases? My datasource type is mysql
    Pulkit Singhal
    @pulkitsinghal
    @kamal0808 might have something to say on this topic
    pookdeveloper
    @pookdeveloper
    @pookdeveloper
    Hello how can i defined only user with role admin can create a new user???
    i try this but not work..
    {
    "accessType": "EXECUTE",
    "principalType": "ROLE",
    "principalId": "admin",
    "permission": "ALLOW",
    "property": "create"
    },
    i am a nob in loopback .. sorry :(
    Alex Pepper
    @alexanderpepper
    Hi all, I'm looking to understand what the index property represents in the datasources.json definition
      "elasticSearchDB": {
        "connector": "es",
        "name": "elasticSearchDB",
        "index": "whatGoesHere?", ...
    My understanding is an index is something defined by a mapping, but this is outside of the mappings property
    Alex Pepper
    @alexanderpepper
    ^ Figured out my question
    Bharath Reddy Kontham
    @bharathkontham

    Hi all,

    Updated Elastcsearch 6.x connector to 1.1.0
    https://www.npmjs.com/package/loopback-connector-esv6

    @pulkitsinghal / administrators, can we move old module which supports 5.x and older to 5.x branch and merge esv6 to master to make it default.

    I'm not seeing any active development for 5.x module

    Bharath Reddy Kontham
    @bharathkontham

    Hi all,

    published Elasticsearch 6.x connector 1.2.0
    https://www.npmjs.com/package/loopback-connector-esv6

    added support for replaceById and replaceOrCreate methods

    pookdeveloper
    @pookdeveloper
    @pookdeveloper
    Hello how can i defined only user with role admin can create a new user???
    i try this but not work..
    {
    "accessType": "EXECUTE",
    "principalType": "ROLE",
    "principalId": "admin",
    "permission": "ALLOW",
    "property": "create"
    },
    i am a nob in loopback .. sorry :(
    I have already do what i want
    Hello, any way to use a File for all logs in loopback ??? for my production app ???
    rhlr
    @rhlr
    Is there any way to combine near queries with multi_match ? I'm trying to use and operator but the multi_match query has no effect on the result.
    {"where":{"and":[{"geo":{"near":{"lat":30.78,"lng":76.69}}},{"native":{"query":{"multi_match":{"query":"python","fields":["title","tags","description"],"type":"most_fields"}}}}]}}
    indrasena
    @indrasenakatam

    loopback 4 connector for ElasticSearch.
    I am working on loopback4 with Elasticsearch. I am created datasource.json file like this

    {
    "name": "customer",
    "connector": "esv6",
    "index": "index_name",
    "hosts": [
    {
    "protocol": "http",
    "host": "127.0.0.1",
    "port": 9200
    }
    ],
    "apiVersion": "6.5",
    "defaultSize": "100",
    "requestTimeout": 30000,
    "log": "trace",
    "mappingType": "basedata",
    "mappings": [],
    "mappingProperties": {

     "......."
    
    "id": {
      "type": "keyword",
      "index": true
    },
    
    "docType": {
      "type": "keyword",
      "index": true
    }
    
    }

    }
    }

    And my model having same id property like this
    @property({
    type: "string",
    id: true,
    generated: true,
    })
    id: string;

    using => "loopback-connector-esv6": "^1.3.0"

    but i am not able to mapping properly...not sure . because ,i am able create (POST) a model object with auto generated id (_id)..but using this id we are not able to find/fetch any data. except POST other APIS are not working..

    So could you please suggest to help on this ..
    how to connect elastic search using loopback4.

    Arthur
    @autocompletedfield
    Hi, could anyone explain me the actual use of this connector? Do I still have to save data manually to elasticsearch instance to be able to fetch it or there is other way of doing things here?
    ijhar
    @ijhar8
    have anyone have git repo of loopback-jwt-passport ..? lb3
    Bharath Reddy Kontham
    @bharathkontham
    Hi all
    Just want to know if we still need elastic 5.x support
    I want to upgrade base module loopback-connector-es to support both 6.x and 7.x
    and drop support for elastic versions <6
    Bharath Reddy Kontham
    @bharathkontham
    Removed stale branches from repository
    New releases will start with version 2.0.0
    Bharath Reddy Kontham
    @bharathkontham
    @pulkitsinghal add me (bharathkontham) as collaborator for npm module https://www.npmjs.com/package/loopback-connector-es
    Bharath Reddy Kontham
    @bharathkontham
    This version supports both versions 6 and 7.
    Master branch is updated with this code
    YueXiaoqiang
    @ScottYueqiang
    is esv6 compatible with LoopBack 4 as well @bharathkontham
    Bharath Reddy Kontham
    @bharathkontham
    @ScottYueqiang, not tested for Loopback 4.
    will check and support for it
    YueXiaoqiang
    @ScottYueqiang
    okay, thanks
    Andrew Kuktenko
    @AndrewKuktenko

    Hi! Have a problem with elasticsearch query

            "native":
              {
                "sort":["_id"],
                "query":{ query_string: { query: 'companyName:apple' } }
              }}

    no matter which query i am using in DEBUG i always get same result
    '{"sort":["_id"],"query":{"bool":{"must":{"match_all":{}},"filter":[{"term":{"docType":"LeadElastic"}}]}}}
    this issue only when i am using "native" filter
    "where" filter works ok but I need to use "query_string" and only way to use it is "native" filter

    Andrew Kuktenko
    @AndrewKuktenko

    // TODO: native query support must be secured to restrict data access to request model /* if (criteria.native) { filter.body = criteria.native; // assume that the developer has provided ES compatible DSL } */

    Found this in source code

    Is it will be available soon?
    Lucio
    @L-Luciano
    Hello
    Erwann Mest
    @kud
    Hey. I would like to know if this connector works on LoopBack v4?
    Rifa Achrinza
    @achrinza
    @kud Technically, it should. Lb4 uses a wrapper to make use of existing juggler-based connectors.
    Erwann Mest
    @kud
    Okay thanks
    Lucio
    @L-Luciano
    Yes, it works fine for loopback's filters.
    balu-ce
    @balu-ce
    Is aggregation query is supported in elasticsearch connector and also I need a sample model and repo file for implementing loopback 4. can anyone please provide that?
    Bharath Reddy Kontham
    @bharathkontham
    @balu-ce , aggregation is not supported, removed native query support for security reasons.
    @/all, I have added support for elasticsearch _source filter.
    New version is 2.0.1
    Will release update with search_after support.
    I'm also working on Loopback 4 official support, it will be available by May 30.
    Bharath Reddy Kontham
    @bharathkontham

    // TODO: native query support must be secured to restrict data access to request model /* if (criteria.native) { filter.body = criteria.native; // assume that the developer has provided ES compatible DSL } */

    Found this in source code

    @AndrewKuktenko , not planning for this now in connector as it requires us to create a property in model to hold aggregation data.
    I would suggest to implement custom remote methods or a mixin for aggregation support.

    You can always use esclient in your loopback code.

    const myesclient = MyModel.getDataSource().connector.db;

    // use es client search method for aggregations
    myesclient.search(...)

    Bharath Reddy Kontham
    @bharathkontham
    @all,
    Added elastic searchnext support for connector
    new version 2.1.0
    check readme for more details on how to use feature.