GitHub user afs opened a pull request:

    https://github.com/apache/jena/pull/236

    No stacktrace on regex errors.  Cancel/close during sorting.

    Changes for:
    
    "runtime regex pattern and many many log messages"
    
https://lists.apache.org/thread.html/0d6042871739323716346ebfff76e64ede7c39a52eacbc0ab17d6d3c@%3Cdev.jena.apache.org%3E
    
    "Bug in SortedDataBag?"
    
https://lists.apache.org/thread.html/be3ecf8f41b03a747f6bab78a072ca55b2ea1a07a6d7ae1e53600ac5@%3Cdev.jena.apache.org%3E


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afs/jena epimorphics_reports

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #236
    
----
commit 95711fa4dce69bfca25a18c3393549ee4136addc
Author: Andy Seaborne <[email protected]>
Date:   2017-04-05T12:10:31Z

    Make runtime regex pattern errors a ExprEvalException.
    
    ExprEvalException does not have a stacktrace
    
    A regex error a "syntax error" is a parse failure if it occurs
    for a fix regex pattern and a logged runtime eval failure if compiled
    dynamically during query execution.  The FILTER will eval to false.
    
    No stacktrace is printed for the logged runtime exception.

commit a4d667fc6e5996abc7049d09a90b38193b6658ad
Author: Andy Seaborne <[email protected]>
Date:   2017-04-05T12:11:41Z

    Implement closeIterator. Call close on a DataBag cancel.

commit 5e88def32bad06a4e9c98b65abd2657b2651d2e8
Author: Andy Seaborne <[email protected]>
Date:   2017-04-05T14:41:11Z

    regex pattern (RegexXerces) errors a ExprEvalException.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to