[jira] [Commented] (NUTCH-2619) protocol-okhttp: allow to keep partially fetched docs as truncated

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (NUTCH-2619) protocol-okhttp: allow to keep partially fetched docs as truncated

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/NUTCH-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539887#comment-16539887 ]

ASF GitHub Bot commented on NUTCH-2619:
---------------------------------------

sebastian-nagel opened a new pull request #361: NUTCH-2619 protocol-okhttp: allow to keep partially fetched docs as truncated
URL: https://github.com/apache/nutch/pull/361
 
 
   If http.partial.truncated is true and there is already content fetched, the content is returned as successful response but marked as truncated. Tested by disconnecting network while fetching an overlong documents (10 MB).
   
   PR includes and is based on fix for NUTCH-2618.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


> protocol-okhttp: allow to keep partially fetched docs as truncated
> ------------------------------------------------------------------
>
>                 Key: NUTCH-2619
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2619
>             Project: Nutch
>          Issue Type: Improvement
>          Components: protocol
>    Affects Versions: 1.15
>            Reporter: Sebastian Nagel
>            Priority: Minor
>             Fix For: 1.16
>
>
> Sometimes fetching a larger document times out after some content has already been downloaded. For some use cases it may be better to save this partially fetched document and mark it as truncated, instead of retrying the fetch later (may fail for the same reason again).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)