Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-918

Enable drop all entailments and re-compute entailments from workbench

    Details

    • Type: New Feature
    • Status: Done
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: BLAZEGRAPH_RELEASE_1_5_1
    • Fix Version/s: BLAZEGRAPH_2_2_0
    • Component/s: Workbench
    • Labels:
      None

      Description

      Provide mechanisms in the workbench to:

      • drop entailments (SPARQL UPDATE call)
      • force the recompute of the closure (SPARQL UPDATE call)

      I suggest that we do not add a method to enable / disable closure as a feature on the database at this time. This requires a global row store update. I would rather put together a meta ticket of GRS features that can be enabled and disabled and then bring in those changes in another release. (Another example would be enable/disable of the full text index vs rebuild of the full text index).

        Issue Links

          Activity

          Hide
          bryanthompson bryanthompson added a comment -

          This approach seems Ok.

          The advantage of doing this through SPARQL UPDATE is that you have visibility into long running operations, and database-at-once closure can be a very long running operation (depending on the data scale).

          Any new servlet also needs to be declared in code in NanoSparqlServer as well as in web.xml.

          Show
          bryanthompson bryanthompson added a comment - This approach seems Ok. The advantage of doing this through SPARQL UPDATE is that you have visibility into long running operations, and database-at-once closure can be a very long running operation (depending on the data scale). Any new servlet also needs to be declared in code in NanoSparqlServer as well as in web.xml.
          Hide
          bryanthompson bryanthompson added a comment -

          Assigned to Brad Bebee to triage. We now support features to enable/disable truth maintenance. Do these need to be exposed to the workbench per this ticket.

          Show
          bryanthompson bryanthompson added a comment - Assigned to Brad Bebee to triage. We now support features to enable/disable truth maintenance. Do these need to be exposed to the workbench per this ticket.
          Hide
          beebs Brad Bebee added a comment -

          Assigned to igorkim to put in the backlog. This should likely be a 2.0 release feature.

          Show
          beebs Brad Bebee added a comment - Assigned to igorkim to put in the backlog. This should likely be a 2.0 release feature.
          Hide
          bryanthompson bryanthompson added a comment - - edited

          My inclination is to provide mechanisms in the workbench to

          • drop entailments (SPARQL UPDATE call)
          • force the recompute of the closure (SPARQL UPDATE call)

          However, I suggest that we do not add a method to enable / disable closure as a feature on the database. This requires a global row store update. I would rather put together a meta ticket of GRS features that can be enabled and disabled and then bring in those changes in another release. (Another example would be enable/disable of the full text index vs rebuild of the full text index).

          Show
          bryanthompson bryanthompson added a comment - - edited My inclination is to provide mechanisms in the workbench to drop entailments (SPARQL UPDATE call) force the recompute of the closure (SPARQL UPDATE call) However, I suggest that we do not add a method to enable / disable closure as a feature on the database. This requires a global row store update. I would rather put together a meta ticket of GRS features that can be enabled and disabled and then bring in those changes in another release. (Another example would be enable/disable of the full text index vs rebuild of the full text index).
          Hide
          bryanthompson bryanthompson added a comment -

          I have updated the ticket to refocus it on the workbench.

          Show
          bryanthompson bryanthompson added a comment - I have updated the ticket to refocus it on the workbench.
          Show
          maria.krokhaleva maria.krokhaleva added a comment - PR: https://github.com/SYSTAP/bigdata/pull/431

            People

            • Assignee:
              igorkim igorkim
              Reporter:
              tobycraig tobycraig
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: