Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Enabler:
      Orion

      Description

      Hello,

      We have two major issues with query forwarding while using the Orion CB

      1. Orion is not forwarding the pagination parameters (limit, offset) when
      they are used. In addition, when reviewed the log of our Context Provider
      we have verified that the request of entities are being requested one to
      one from Orion.

      Also, after executing a query with pagination parameters, it turns all the
      entities without paignation, and returns the following error at the end,
      with code 200!!:

      Issue: https://github.com/telefonicaid/fiware-orion/issues/847

      "errorCode":

      { "code": "200", "reasonPhrase": "OK", "details": "Count: 0" }

      We wonder if we are missing some parameter in the registration of the
      provider to Orion, we are aware of some limitation using the NGSIv2 so we
      have enabled the integration by using the NGSI v1 legacy mode between Orion
      and our Custom Provider. ¿any idea fix the pagination forwarding issue?

      2. Similar issue has been found with query filtering, that are not
      forwarded to the provider. Actually, it seems Orion doesn't send the filter
      in the POST /v1/queryContext to provider. An issue corresponding to this
      limitation has been created but not resolved yet
      https://github.com/telefonicaid/fiware-orion/issues/2282.

      ¿Is there any advance in the support of these functionalities or workaround
      to address it nowadays?

      Thanks in advance

      Regards
      Ailema

      __________________________________________________________________________________________

      You can get more information about our cookies and privacy policies on the following links:

      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: =?UTF-8?Q?Ailema_V=C3=A1zquez_Garc=C3=ADa?= <avazquez@bettergy.es>]

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        44d 23h 51m 1 Jason Fox 30/Aug/18 11:50 AM
        In Progress In Progress Answered Answered
        3s 1 Jason Fox 30/Aug/18 11:50 AM
        Answered Answered Closed Closed
        2s 1 Jason Fox 30/Aug/18 11:50 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        backlogmanager Backlog Manager made changes -
        Summary [Fiware-tech-help] [frontierCities2] FIWARE.Request.Tech..
        jason.fox Jason Fox made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        jason.fox Jason Fox made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        jason.fox Jason Fox made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        jason.fox Jason Fox added a comment -

        eMail sent to User

        Show
        jason.fox Jason Fox added a comment - eMail sent to User
        Hide
        jason.fox Jason Fox added a comment - - edited

        The problem described is restating two issues that are already opened on the Orion repository:

        These issues are related with limitations in the NGSIv1-based forwarding (also known as "legacy forwarding"). NGSIv1-based forwarding works pretty good when in 1-to-1 forwarding cases, but when 1-to-N scenarios come into play there are problems that are not easy to address (specially when merge-and-sort of all partial results from CPrs is required in the CB).

        There is a proposal in place for a new NGSIv2-based forwarding mechanism- Context Source Forwarding Specification https://github.com/Fiware/specifications/pull/2 - need to confirm that this specification addresses both issues so that the issue can be solved with the next iteration of Orion rather than hacking a fix into legacy v1 NGSI

        Show
        jason.fox Jason Fox added a comment - - edited The problem described is restating two issues that are already opened on the Orion repository: https://github.com/telefonicaid/fiware-orion/issues/847 https://github.com/telefonicaid/fiware-orion/issues/2282 These issues are related with limitations in the NGSIv1-based forwarding (also known as "legacy forwarding"). NGSIv1-based forwarding works pretty good when in 1-to-1 forwarding cases, but when 1-to-N scenarios come into play there are problems that are not easy to address (specially when merge-and-sort of all partial results from CPrs is required in the CB). There is a proposal in place for a new NGSIv2-based forwarding mechanism- Context Source Forwarding Specification https://github.com/Fiware/specifications/pull/2 - need to confirm that this specification addresses both issues so that the issue can be solved with the next iteration of Orion rather than hacking a fix into legacy v1 NGSI
        Hide
        jmcantera Jose Manuel Cantera added a comment -

        assigning Jason as I'm going on vacation until end of the month.

        Show
        jmcantera Jose Manuel Cantera added a comment - assigning Jason as I'm going on vacation until end of the month.
        jmcantera Jose Manuel Cantera made changes -
        Assignee Jose Manuel Cantera [ jmcantera ] Jason Fox [ jason.fox ]
        veronika Veronika Vlnkova made changes -
        Assignee Jose Manuel Cantera [ jmcantera ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        fw.ext.user FW External User created issue -

          People

          • Assignee:
            jason.fox Jason Fox
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: