Uploaded image for project: 'Accumulo'
  1. Accumulo
  2. ACCUMULO-2059

Namespace constraints easily get clobbered by table constraints

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.6.0
    • Fix Version/s: 1.9.0, 2.0.0
    • Component/s: client
    • Labels:
      None

      Description

      This is why ShellServerIT#namespaces is failing currently. When you create a table with the default configurations, that includes a DefaultKeySizeConstraint at constraint.1. This overlaps the namespaces defined constraint.1, which is a NumericValueConstraint for the test.

      The issue is I'm not sure if this is accepted behavior or not. Constraint settings are already sorta wonky, but this is not the time to rewrite it. Before I fix it, I just need to know if that is tolerable behavior or if we want namespace constraints to start at a different value, like constraint.101 to minimize impact. Thoughts are requested.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vines John Vines
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: