Nguyen Huu Nhat created CONNECTORS-1738:
-------------------------------------------

             Summary: Suggestion for adding function that allows setting 
timeout values for Elasticsearch Output Connector
                 Key: CONNECTORS-1738
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1738
             Project: ManifoldCF
          Issue Type: Improvement
            Reporter: Nguyen Huu Nhat
         Attachments: EditConnection.PNG, ViewConnection.PNG, patch.txt

Hi there,

For Elasticsearch Output Connector, during use, I have exeperienced cases that 
required the values of *socketTimeout* and *connectionTimeout* to be increased.
However, as those values are being hardcoded within the source code as 
900000(ms) and 60000(ms) respectively, it is quite troublesome to update them 
in cases mentioned above.

For this reason, instead of hardcoding, I think it would be better that the 
values of *socketTimeout* and *connectionTimeout* can be edited through WebUI, 
on the connection setting screen.

In ManifoldCF, there are also a few other connectors that support setting 
*socketTimeout* and {*}connectionTimeout{*}, such as Generic, Confluence, etc.
Therefore, I would like to suggest modifying the ElasticSearch Output 
Connector's source code to allow setting *socketTimeout* and 
*connectionTimeout* value when it is needed.
h3. +*1. Connector Name*+

ElasticSearch Output Connector
h3. +*2. Improvement Detail*+

On connection setting screen (WebUI), add handling method that enable value 
setting for *socketTimeout* and *connectionTimeout*
※The default value for *socketTimeout* and *connectionTimeout* are still 900000 
and 60000 (ms) as they are.

The connection setting screen will look like below:
!EditConnection.PNG!
h3. +*3. Suggested source code (based on release 2.22.1)*+

Because the content is edited in many files & the number of LOC is quite large,
I will attach the patch file here, please check it out.
[^patch.txt]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to