Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: 1.2.0 rc1
    • Component/s: Core
    • Labels:
      None

      Description

      Currently any select statement that uses a token() predicate breaks with "Bad Input"

      After tracing the logic this error is caused in getTokenBounds because it assumes the token term is an actual token string what will pass the tokenizer

      1. 5050.txt
        0.6 kB
        T Jake Luciani

        Activity

        T Jake Luciani created issue -
        T Jake Luciani made changes -
        Field Original Value New Value
        Attachment 5050.txt [ 12560285 ]
        Hide
        Sylvain Lebresne added a comment -

        +1, committed, thanks

        Show
        Sylvain Lebresne added a comment - +1, committed, thanks
        Sylvain Lebresne made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee T Jake Luciani [ tjake ]
        Fix Version/s 1.2.0 rc1 [ 12323481 ]
        Fix Version/s 1.2.0 [ 12323243 ]
        Resolution Fixed [ 1 ]
        Gavin made changes -
        Workflow no-reopen-closed, patch-avail [ 12741651 ] patch-available, re-open possible [ 12753745 ]
        Gavin made changes -
        Workflow patch-available, re-open possible [ 12753745 ] reopen-resolved, no closed status, patch-avail, testing [ 12758880 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        10h 21m 1 Sylvain Lebresne 11/Dec/12 07:55

          People

          • Assignee:
            T Jake Luciani
            Reporter:
            T Jake Luciani
            Reviewer:
            Sylvain Lebresne
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development