Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8677

[fiware-stackoverflow] Problems with v1/queryContext needed for SpagoBI integration

    Details

      Description

      Created question in FIWARE Q/A platform on 09-05-2017 at 18:05
      Please, ANSWER this question AT http://stackoverflow.com/questions/43875326/problems-with-v1-querycontext-needed-for-spagobi-integration

      Question:
      Problems with v1/queryContext needed for SpagoBI integration

      Description:
      In version 1.7.0 of Orion CB running the docker version in Docker for Windows,
      if I create a simple object doing POST http://localhost:1026/v1/updateContext

      with the body:

      {
      "contextElements": [
      {
      "type": "Car",
      "id": "myNewCar",
      "attributes": [

      { "name": "maxSpeed", "type": "integer", "value": "220" }

      ]
      }
      ],
      "updateAction": "APPEND"
      }

      I get the answer:

      {
      "contextResponses": [
      {
      "contextElement": {
      "type": "Car",
      "isPattern": "false",
      "id": "myNewCar",
      "attributes": [

      { "name": "maxSpeed", "type": "integer", "value": "" }

      ]
      },
      "statusCode":

      { "code": "200", "reasonPhrase": "OK" }

      }
      ]
      }

      Then, if I do POST http://localhost:1026/v1/queryContext with the same headers and the same components with the body

      {
      "entities": [

      { "type": "Car", "isPattern": "false", "id": "myNewCar" }

      ]
      }

      I get the following:

      {
      "errorCode":

      { "code": "404", "reasonPhrase": "No context element found" }

      }

      Which shouldn't be problematic (I can query the entities with v2 API, for instance) if it wasn't needed for integration with data representation tools such as SpagoBI as documented in http://spagobi.readthedocs.io/en/latest/user/NGSI/README/

      What can I do? I am doing something wrong with the context provision?

      Thanks!

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        14h 59m 1 Backlog Manager 10/May/17 12:04 PM
        In Progress In Progress Answered Answered
        1h 1m 1 Fermín Galán 10/May/17 1:06 PM
        Answered Answered Closed Closed
        1s 1 Fermín Galán 10/May/17 1:06 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fermin Fermín Galán made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fermin Fermín Galán made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        Hide
        fermin Fermín Galán added a comment -

        Self solved by the user himself.

        Show
        fermin Fermín Galán added a comment - Self solved by the user himself.
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        Description
        Created question in FIWARE Q/A platform on 09-05-2017 at 18:05
        {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/43875326/problems-with-v1-querycontext-needed-for-spagobi-integration


        +Question:+
        Problems with v1/queryContext needed for SpagoBI integration

        +Description:+
        In version 1.7.0 of Orion CB running the docker version in Docker for Windows,
        if I create a simple object doing POST http://localhost:1026/v1/updateContext

        with the body:

        {
            "contextElements": [
                {
                    "type": "Car",
                    "id": "myNewCar",
                    "attributes": [
                        {
                            "name": "maxSpeed",
                            "type": "integer",
                            "value": "220"
                        }
                    ]
                }
            ],
            "updateAction": "APPEND"
        }


        I get the answer:

        {
          "contextResponses": [
            {
              "contextElement": {
                "type": "Car",
                "isPattern": "false",
                "id": "myNewCar",
                "attributes": [
                  {
                    "name": "maxSpeed",
                    "type": "integer",
                    "value": ""
                  }
                ]
              },
              "statusCode": {
                "code": "200",
                "reasonPhrase": "OK"
              }
            }
          ]
        }


        Then, if I do POST http://localhost:1026/v1/queryContext with the same headers and the same components with the body

        {
            "entities": [
                {
                    "type": "Car",
                    "isPattern": "false",
                    "id": "myNewCar"
                }
            ]
        }


        I get the following:

        {
          "errorCode": {
            "code": "404",
            "reasonPhrase": "No context element found"
          }
        }


        Which shouldn't be problematic (I can query the entities with v2 API, for instance) if it wasn't needed for integration with data representation tools such as SpagoBI as documented in http://spagobi.readthedocs.io/en/latest/user/NGSI/README/

        What can I do? I am doing something wrong with the context provision?

        Thanks!
        Created question in FIWARE Q/A platform on 09-05-2017 at 18:05
        {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/43875326/problems-with-v1-querycontext-needed-for-spagobi-integration


        +Question:+
        Problems with v1/queryContext needed for SpagoBI integration

        +Description:+
        In version 1.7.0 of Orion CB running the docker version in Docker for Windows,
        if I create a simple object doing POST http://localhost:1026/v1/updateContext

        with the body:

        {
            "contextElements": [
                {
                    "type": "Car",
                    "id": "myNewCar",
                    "attributes": [
                        {
                            "name": "maxSpeed",
                            "type": "integer",
                            "value": "220"
                        }
                    ]
                }
            ],
            "updateAction": "APPEND"
        }


        I get the answer:

        {
          "contextResponses": [
            {
              "contextElement": {
                "type": "Car",
                "isPattern": "false",
                "id": "myNewCar",
                "attributes": [
                  {
                    "name": "maxSpeed",
                    "type": "integer",
                    "value": ""
                  }
                ]
              },
              "statusCode": {
                "code": "200",
                "reasonPhrase": "OK"
              }
            }
          ]
        }


        Then, if I do POST http://localhost:1026/v1/queryContext with the same headers and the same components with the body

        {
            "entities": [
                {
                    "type": "Car",
                    "isPattern": "false",
                    "id": "myNewCar"
                }
            ]
        }


        I get the following:

        {
          "errorCode": {
            "code": "404",
            "reasonPhrase": "No context element found"
          }
        }


        Which shouldn't be problematic (I can query the entities with v2 API, for instance) if it wasn't needed for integration with data representation tools such as SpagoBI as documented in http://spagobi.readthedocs.io/en/latest/user/NGSI/README/

        What can I do? I am doing something wrong with the context provision?

        Thanks!
        HD-Chapter Data [ 10838 ]
        fla Fernando Lopez made changes -
        Assignee Fermín Galán [ fermin ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-10 12:05|UPDATED status: transition Answer| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-10 12:05|UPDATED status: transition Answer| # answers= 1, accepted answer= True
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-09 21:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-09 21:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            fermin Fermín Galán
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: