Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.7.0
    • Other
    • None

    Description

      When a query is issued, the connector ensures that any streaming resultset will be fully read from the socket before issuing a new command.
      This permits to ensure the socket state.

      Adding a new option `ensureSocketState` that when enable will ensure that the socket buffer is empty before issuing new command. (this doesn't concern pipelining commands). If data is present in socket. An error will be raised, throwing the content of socket data to permit identification of error. The goal of this option is mainly for debugging.

      This functionality add a few overheads so will be disabled by default

      If enable, this option will permit to identify issue like CONJ-826.

      Attachments

        Activity

          diego dupin Diego Dupin created issue -
          diego dupin Diego Dupin made changes -
          Field Original Value New Value
          Description When a query is issued, the connector ensures that any streaming resultset will be fully read from the socket before issuing a new command.
          This permits to ensure the socket state.

          Adding a new option `ensureSocketState` that when enable will ensure that the socket buffer is empty before issuing new command. (this doesn't concern pipelining commands).
          This functionality add a few overheads so will be disabled by default

          The goal of this option is mainly for debugging.
          If enable, this option will permit to identify issue like CONJ-826.
           
          When a query is issued, the connector ensures that any streaming resultset will be fully read from the socket before issuing a new command.
          This permits to ensure the socket state.

          Adding a new option `ensureSocketState` that when enable will ensure that the socket buffer is empty before issuing new command. (this doesn't concern pipelining commands). If data is present in socket. An error will be raised, throwing the content of socket data to permit identification of error. The goal of this option is mainly for debugging.

          This functionality add a few overheads so will be disabled by default

          If enable, this option will permit to identify issue like CONJ-826.
           
          diego dupin Diego Dupin made changes -
          issue.field.resolutiondate 2020-09-10 15:30:18.0 2020-09-10 15:30:18.501
          diego dupin Diego Dupin made changes -
          Component/s Other [ 12201 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 113414 ] MariaDB v4 [ 135196 ]

          People

            diego dupin Diego Dupin
            diego dupin Diego Dupin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.