Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-1927

Gherkin scenario expects list with duplicates, but receives g:Set

    XMLWordPrintableJSON

    Details

      Description

      The scenario g_V_storeXaX_byXoutEXcreatedX_countX_out_out_storeXaX_byXinEXcreatedX_weight_sumX expects

      | result |
      | d[1].l |
      | d[1].l |
      | d[0].l |
      | d[0].l |
      | d[0].l |
      | d[2].l |
      | d[1.0].d |
      | d[1.0].d |
      

      but we receive this from the server:

      {
          "@type": "g:Set",
          "@value": [
              {
                  "@type": "g:Int64",
                  "@value": 1
              },
              {
                  "@type": "g:Int64",
                  "@value": 1
              },
              {
                  "@type": "g:Int64",
                  "@value": 0
              },
              {
                  "@type": "g:Int64",
                  "@value": 0
              },
              {
                  "@type": "g:Int64",
                  "@value": 0
              },
              {
                  "@type": "g:Int64",
                  "@value": 2
              },
              {
                  "@type": "g:Double",
                  "@value": 1
              },
              {
                  "@type": "g:Double",
                  "@value": 1
              }
          ]
      }
      

      The set returned by the server contains 4 duplicates that shouldn't be part of the expected result in the scenario.

      Unfortunately, while working on TINKERPOP-1865 we noticed that gremlin-python and gremlin-javascript fail when the scenario is fixed like that. So those two GLVs probably need to be fixed to handle g:Set correctly.

      After fixing the scenario, it can be removed from the list of ignored scenarios in Gremlin.Net.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                spmallette Stephen Mallette
                Reporter:
                Florian Hockmann Florian Hockmann
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: