Uploaded image for project: 'Apache Jena'
  1. Apache Jena
  2. JENA-210

Make QueryEngineHttp more configurable

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • ARQ 2.9.0
    • ARQ 2.9.1
    • ARQ

    Description

      The current QueryEngineHttp is somewhat limited in that the Accept header is hardcoded to SPARQL Results XML or RDF/XML depending on the usage of the engine and there are a number of other features lacking including timeouts and support for requesting and reading compressed content.

      The submitted patch here adds the following features:

      1 - Configurable Content Type support

      A QueryEngineHttp instance can be configured to request different content types as required by the users. For CONSTRUCT/DESCRIBE whether the requested content type is valid is verified using RIOT and the parser for reading responses into models automatically selected. For ASK/SELECT the supported content types are defined in hard-coded lists and the parser selected via if statements.

      In the future it is envisaged that ASK/SELECT supported format detection could be improved by wiring into whatever new machinery around handling result formats that ARQ/RIOT eventually supplies

      2 - Configuration Timeouts

      Support for configuring Connection and Read Timeouts for queries

      3 - GZip and Deflate Compression Support

      Support for specifying that the client will allow GZip/Deflate encoded content to be sent to it and for ensuring that the returned InputStream gets appropriately wrapped so the content is decompressed as read

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            andy Andy Seaborne
            rvesse Rob Vesse
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment