Details

      Description

      when using SPARQL update through the NSS, the standard does not specify the contents of the return document.
      Blazegraph chooses to echo back the SPARQL update request.
      If the request is large, this is not an entirely trivial operation, and we would disable it if we could.

      This could be done either on a per request basis using a parameter or similar, or maybe even as an option to the blazegraph instance.

        Issue Links

          Activity

          Hide
          beebs Brad Bebee added a comment -

          Per discussion with igorkim, we will make the default to not echo the SPARQL and provide the option to echo back the query.

          Show
          beebs Brad Bebee added a comment - Per discussion with igorkim , we will make the default to not echo the SPARQL and provide the option to echo back the query.
          Hide
          beebs Brad Bebee added a comment -

          igorkim Can you confirm that this one is implemented? I don't see a version on the ticket.

          Show
          beebs Brad Bebee added a comment - igorkim Can you confirm that this one is implemented? I don't see a version on the ticket.

            People

            • Assignee:
              igorkim igorkim
              Reporter:
              jeremycarroll jeremycarroll
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: