gremlin order by with coalesce duplicates some values












0















In some cases, I get inexplicable result when I use order().by(...) with coalesce(...).
Using the standard Modern graph,



gremlin> g.V()
.hasLabel("person")
.out("created")
.coalesce(values("name"), constant("x"))
.fold()
==>[lop,lop,ripple,lop]


But if I sort by name before the coalesce I get 9 lop instead of 3:



gremlin> g.V()
.hasLabel("person")
.out("created")
.order().by("name")
.coalesce(values("name"), constant("x"))
.fold()
==>[lop,lop,lop,lop,lop,lop,lop,lop,lop,ripple]


Why the number of elements differs between the two queries ?










share|improve this question



























    0















    In some cases, I get inexplicable result when I use order().by(...) with coalesce(...).
    Using the standard Modern graph,



    gremlin> g.V()
    .hasLabel("person")
    .out("created")
    .coalesce(values("name"), constant("x"))
    .fold()
    ==>[lop,lop,ripple,lop]


    But if I sort by name before the coalesce I get 9 lop instead of 3:



    gremlin> g.V()
    .hasLabel("person")
    .out("created")
    .order().by("name")
    .coalesce(values("name"), constant("x"))
    .fold()
    ==>[lop,lop,lop,lop,lop,lop,lop,lop,lop,ripple]


    Why the number of elements differs between the two queries ?










    share|improve this question

























      0












      0








      0








      In some cases, I get inexplicable result when I use order().by(...) with coalesce(...).
      Using the standard Modern graph,



      gremlin> g.V()
      .hasLabel("person")
      .out("created")
      .coalesce(values("name"), constant("x"))
      .fold()
      ==>[lop,lop,ripple,lop]


      But if I sort by name before the coalesce I get 9 lop instead of 3:



      gremlin> g.V()
      .hasLabel("person")
      .out("created")
      .order().by("name")
      .coalesce(values("name"), constant("x"))
      .fold()
      ==>[lop,lop,lop,lop,lop,lop,lop,lop,lop,ripple]


      Why the number of elements differs between the two queries ?










      share|improve this question














      In some cases, I get inexplicable result when I use order().by(...) with coalesce(...).
      Using the standard Modern graph,



      gremlin> g.V()
      .hasLabel("person")
      .out("created")
      .coalesce(values("name"), constant("x"))
      .fold()
      ==>[lop,lop,ripple,lop]


      But if I sort by name before the coalesce I get 9 lop instead of 3:



      gremlin> g.V()
      .hasLabel("person")
      .out("created")
      .order().by("name")
      .coalesce(values("name"), constant("x"))
      .fold()
      ==>[lop,lop,lop,lop,lop,lop,lop,lop,lop,ripple]


      Why the number of elements differs between the two queries ?







      gremlin tinkerpop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 13:21









      To-omTo-om

      33




      33
























          1 Answer
          1






          active

          oldest

          votes


















          1














          That looks like a bug - I've created an issue in JIRA. There is a workaround but first consider that your traversal isn't really going to work even with the bug set aside, order() will fail because you're referencing a key that possibly doesn't exist in the by() modulator. So you need to account for that differently:



          g.V().
          hasLabel("person").
          out("created").
          order().by(coalesce(values('name'),constant('x')))


          I then used choose() to do what coalesce() is supposed to do:



          g.V().
          hasLabel("person").
          out("created").
          order().by(coalesce(values('name'),constant('x'))).
          choose(has("name"),values('name'),constant('x')).
          fold()


          and that seems to work fine.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482054%2fgremlin-order-by-with-coalesce-duplicates-some-values%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            That looks like a bug - I've created an issue in JIRA. There is a workaround but first consider that your traversal isn't really going to work even with the bug set aside, order() will fail because you're referencing a key that possibly doesn't exist in the by() modulator. So you need to account for that differently:



            g.V().
            hasLabel("person").
            out("created").
            order().by(coalesce(values('name'),constant('x')))


            I then used choose() to do what coalesce() is supposed to do:



            g.V().
            hasLabel("person").
            out("created").
            order().by(coalesce(values('name'),constant('x'))).
            choose(has("name"),values('name'),constant('x')).
            fold()


            and that seems to work fine.






            share|improve this answer




























              1














              That looks like a bug - I've created an issue in JIRA. There is a workaround but first consider that your traversal isn't really going to work even with the bug set aside, order() will fail because you're referencing a key that possibly doesn't exist in the by() modulator. So you need to account for that differently:



              g.V().
              hasLabel("person").
              out("created").
              order().by(coalesce(values('name'),constant('x')))


              I then used choose() to do what coalesce() is supposed to do:



              g.V().
              hasLabel("person").
              out("created").
              order().by(coalesce(values('name'),constant('x'))).
              choose(has("name"),values('name'),constant('x')).
              fold()


              and that seems to work fine.






              share|improve this answer


























                1












                1








                1







                That looks like a bug - I've created an issue in JIRA. There is a workaround but first consider that your traversal isn't really going to work even with the bug set aside, order() will fail because you're referencing a key that possibly doesn't exist in the by() modulator. So you need to account for that differently:



                g.V().
                hasLabel("person").
                out("created").
                order().by(coalesce(values('name'),constant('x')))


                I then used choose() to do what coalesce() is supposed to do:



                g.V().
                hasLabel("person").
                out("created").
                order().by(coalesce(values('name'),constant('x'))).
                choose(has("name"),values('name'),constant('x')).
                fold()


                and that seems to work fine.






                share|improve this answer













                That looks like a bug - I've created an issue in JIRA. There is a workaround but first consider that your traversal isn't really going to work even with the bug set aside, order() will fail because you're referencing a key that possibly doesn't exist in the by() modulator. So you need to account for that differently:



                g.V().
                hasLabel("person").
                out("created").
                order().by(coalesce(values('name'),constant('x')))


                I then used choose() to do what coalesce() is supposed to do:



                g.V().
                hasLabel("person").
                out("created").
                order().by(coalesce(values('name'),constant('x'))).
                choose(has("name"),values('name'),constant('x')).
                fold()


                and that seems to work fine.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 26 '18 at 14:49









                stephen mallettestephen mallette

                25.8k32877




                25.8k32877
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482054%2fgremlin-order-by-with-coalesce-duplicates-some-values%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Lallio

                    Futebolista

                    Jornalista