Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-173

[Feature Request] Implement a mechanism to bypass result set caching for streamed results

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Incomplete
    • None
    • N/A
    • Other
    • None
    • JDBC

    Description

      The streamed result set feature isn't usable in the MariaDB JDBC driver as it always creates a cached result set which means large result sets could consume large amounts of memory leading to out of memory failures. I've doctored the latest version for my own use to bypass result set caching on demand but it would be good if proper result set streaming was supported.

      Attachments

        Issue Links

          duplicates

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CONJ-26 [Feature Request] Implement configurable fetch size and fetch direction for Statement/ResultSet

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

          Task - A task that needs to be done. CONJ-125 Optimize cached ResultSet memory footprint

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

          Activity

            People

              diego dupin Diego Dupin
              GeoffreyR Geoffrey Rutherford
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.