You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# We don't currently support usage of partition routing and IncrementingCountCursor at the
2213
+
# same time because we didn't solve for design questions like what the lookback window would
2214
+
# be as well as global cursor fall backs. We have not seen customers that have needed both
2215
+
# at the same time yet and are currently punting on this until we need to solve it.
2216
+
raiseValueError(
2217
+
f"The low-code framework does not currently support usage of a PartitionRouter and an IncrementingCountCursor at the same time. Please specify only one of these options for stream {stream_name}."
2218
+
)
2211
2219
returnself.create_concurrent_cursor_from_perpartition_cursor( # type: ignore # This is a known issue that we are creating and returning a ConcurrentCursor which does not technically implement the (low-code) StreamSlicer. However, (low-code) StreamSlicer and ConcurrentCursor both implement StreamSlicer.stream_slices() which is the primary method needed for checkpointing
forkey, request_parameterinmodel.requester.request_parameters.items(): # type: ignore # request_parameters is already validated to be a Mapping using _query_properties_in_request_parameters()
3214
+
forkey, request_parameterinmodel.requester.request_parameters.items(): # type: ignore # request_parameters is already validated to be a Mapping using _has_query_properties_in_request_parameters()
0 commit comments