Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3284

Track incompatibilities between Calcite/Phoenix and Phoenix

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      As we get deeper into moving Phoenix to run on top of Calcite, we may find non standard Phoenix-specific syntax which we don't want to support in Phoenix/Calcite. An example might be not supporting != but requiring these to be changed to <>. This epic JIRA can serve as the root for tracking purposes.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: