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

Workspace and backend should not permit an empty namespace name

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: BLAZEGRAPH_RELEASE_1_5_3
    • Component/s: None
    • Labels:
      None

      Description

      The backend should modified to correctly reject an empty string as a namespace name. A unit test should be added for this. Namespaces may be unicode. They may not include the "." character since this is used to indicate a series of components in an index name (e.g., kb.spo.SPO is the name of the SPO index).

      The workbench should be modified to not allow an empty namespace name when creating a namespace.

      The user guide should be modified to indicate that the namespace name must be non-empty and indicate the allowed form of a namespace name.

        Activity

        Hide
        beebs Brad Bebee added a comment - - edited

        igorkim We have a user with existing blank namespaces. The fix for this should not allow the creation of new namespaces with a blank name, but it should also be tested to make sure that it does not break existing namespaces created before the fix with a blank name.

        Show
        beebs Brad Bebee added a comment - - edited igorkim We have a user with existing blank namespaces. The fix for this should not allow the creation of new namespaces with a blank name, but it should also be tested to make sure that it does not break existing namespaces created before the fix with a blank name.
        Hide
        igorkim igorkim added a comment - - edited

        Brad Bebee, yes the fix does not apply additional restrictions on already existing namespaces. we will ensure that workbench will still work with such names.

        Show
        igorkim igorkim added a comment - - edited Brad Bebee , yes the fix does not apply additional restrictions on already existing namespaces. we will ensure that workbench will still work with such names.
        Hide
        bryanthompson bryanthompson added a comment -

        Can this be closed?

        Show
        bryanthompson bryanthompson added a comment - Can this be closed?
        Hide
        bryanthompson bryanthompson added a comment -

        Assigned to Brad to figure out which release contains this fix and close out the ticket.

        Show
        bryanthompson bryanthompson added a comment - Assigned to Brad to figure out which release contains this fix and close out the ticket.
        Hide
        jjc Jeremy Carroll added a comment -

        As a user with blank namespace names ... which version are blank namespaces prohibited on creation. (I think it was an error on my part using a blank namespace name, and I would have been better served with a 400 error), but I need to check that we move forward appropriately, I am far from convinced that we are not still creating such namespaces

        Show
        jjc Jeremy Carroll added a comment - As a user with blank namespace names ... which version are blank namespaces prohibited on creation. (I think it was an error on my part using a blank namespace name, and I would have been better served with a 400 error), but I need to check that we move forward appropriately, I am far from convinced that we are not still creating such namespaces
        Hide
        jjc Jeremy Carroll added a comment -

        Specifically code that we used creating a new journal off a recent 1.5.3 build does seem to have created a blank namespace, and I will need to change that code once these are prohibited.

        Show
        jjc Jeremy Carroll added a comment - Specifically code that we used creating a new journal off a recent 1.5.3 build does seem to have created a blank namespace, and I will need to change that code once these are prohibited.

          People

          • Assignee:
            beebs Brad Bebee
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated: