Details

    • Type: Sub-task
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: 4.x
    • Component/s: Legacy/CQL
    • Labels:
      None

      Description

      Currently we stream the number of rows back to the client before serializing, which means we need to know how many there are before doing so, which means materializing the entire resultset. We currently get around this with paging which attempts to restrict the amount of materialization done in any step, but supporting streaming entire result sets in one native transport "action" without materializing them all upfront would remove the need for paging in many cases, and would permit resultsets to be streamed with isolation, which most users probably don't realise is broken by paging.

      We can't use this change yet, but the sooner support for this is introduced to the protocol, the more likely it is clients will be able to make use of streaming reads once we're actually able to deliver them.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                benedict Benedict Elliott Smith
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated: