Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-8501

Specify the entity request size when known in HttpSolrClient.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.5, 6.0
    • None
    • None

    Description

      We currently always pass -1 and used chunked encoding. This seems wasteful? Chunked encoding has overhead and we generally know the sizes. Seems like it would be preferable to set the entity size and trigger the Content-Size: header.

      Attachments

        Issue Links

        is related to

        Improvement - An improvement or enhancement to an existing feature or task. SOLR-8669 Non binary responses use chunked encoding because we flush the outputstream early.

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Resolved
        relates to

        Bug - A problem which impairs or prevents the functions of the product. SOLR-8451 We should not call method.abort in HttpSolrClient and HttpSolrCall#remoteQuery should not close streams.

        • Major - Major loss of function.
        • Closed

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

          People

            markrmiller@gmail.com Mark Miller
            markrmiller@gmail.com Mark Miller
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment