Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-16942

ES 5 sink should allow users to select netty transport client

Agile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

      Description

      When assembling the settings for the PreBuiltTransportClient the Elasticsearch5ApiCallBridge first adds the user-provided client and then overrides http/transport types with netty 3.

      This means that users are forced to use netty 3, despite the connector being able to work with a more recent and secure version.

      Settings settings = Settings.builder().put(clientConfig)
      	.put(NetworkModule.HTTP_TYPE_KEY, Netty3Plugin.NETTY_HTTP_TRANSPORT_NAME)
      	.put(NetworkModule.TRANSPORT_TYPE_KEY, Netty3Plugin.NETTY_TRANSPORT_NAME)
      	.build();
      

      We should invert the order in which the settings are added.

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              chesnay Chesnay Schepler
              Reporter:
              chesnay Chesnay Schepler

              Dates

              • Created:
                Updated:
                Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

                Issue deployment