Complete Fetch Phase (for INLINE disposition and JSON_ARRAY format)

[varun-edachali-dbx]

What type of PR is this?

• Feature

Description

Complete the Fetch phase of the SEA implementation for INLINE disposition and JSON_ARRAY format. Introduce a new JsonQueue.

Note that this is not yet feature complete, with some known failures in the following domains (for the SEA backend only):

• retries
• native, complex params
• metadata queries

These will be resolved in future PRs.

How is this tested?

• Unit tests
• E2E Tests
• Manually - using the test scripts invoked in examples/experimental/sea_connector_test.py.
• N/A

The coverage of the key classes by the unit tests are as below:

Module	Statements	Missing	Coverage	Notes
utils.py (JsonQueue class)	15	0	100%	Completely covered
utils.py (SeaResultSetQueueFactory class)	20	0	100%	Completely covered
result_set.py (SeaResultSet class)	155	0	100%	Completely covered
conversion.py	43	0	100%	Completely covered

Related Tickets & Documents

Design Doc
PECOBLR-484

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[jayantsing-db]

Some minor comments. Rest LGTM.

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).