You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Michael J. Carey (JIRA)" <ji...@apache.org> on 2018/11/08 19:22:00 UTC

[jira] [Created] (ASTERIXDB-2477) CREATE INDEX doc is incomplete

Michael J. Carey created ASTERIXDB-2477:
-------------------------------------------

             Summary: CREATE INDEX doc is incomplete
                 Key: ASTERIXDB-2477
                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2477
             Project: Apache AsterixDB
          Issue Type: Bug
          Components: DOC - Documentation
    Affects Versions: 0.9.4
            Reporter: Michael J. Carey
            Assignee: Dmitry Lychagin


Our CREATE INDEX documentation says:

An indexed field is not required to be part of the datatype associated with a dataset if the dataset's datatype is declared as open *and* if the field's type is provided along with its name and if the {{ENFORCED}} keyword is specified at the end of the index definition. {{ENFORCING}} an open field introduces a check that makes sure that the actual type of the indexed field (if the optional field exists in the object) always matches this specified (open) field type.

This is no longer the case AFAIK - I believe we also allow indexing of open fields now without enforcement, right?  (I.e., this was just our initial story.)  This more general case and its behavior need to be elaborated on here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)