feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. #113

Merged

stanislav.hejny merged 9 commits from feat/89 into develop 2025-11-24 13:47:36 +00:00

Conversation 1 Commits 9 Files changed 40 +2687 -1168

stanislav.hejny commented 2025-11-20 14:35:32 +00:00

Member

Copy link

For multipart upload, we defined req-info as the stream name for request itself, this allow us to send out a multi-stream message that contain both the request info and the uploaded content. However, the reverse path doesn't have similar things define. With the newly added pre-signed url feature, when downloading a file, instead of streaming the actual content, the microservice can give a presign url and the amq router will stream the content of that url to client.

This ticket should first define a similar thing for response, like resp-info as the stream name to send an json object about the metadata of the downloaded file, then point to the actual file stream. When sending out the response, the caller should use addressing mode 4 to send the presign url, so the amq library can automatically use it and turns into an inputstream for amq router to use.

For multipart upload, we defined `req-info` as the stream name for request itself, this allow us to send out a multi-stream message that contain both the request info and the uploaded content. However, the reverse path doesn't have similar things define. With the newly added pre-signed url feature, when downloading a file, instead of streaming the actual content, the microservice can give a presign url and the amq router will stream the content of that url to client. This ticket should first define a similar thing for response, like `resp-info` as the stream name to send an json object about the metadata of the downloaded file, then point to the actual file stream. When sending out the response, the caller should use addressing mode 4 to send the presign url, so the amq library can automatically use it and turns into an inputstream for amq router to use.

stanislav.hejny added 1 commit 2025-11-20 14:35:32 +00:00

feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. 1de2d1824b

stanislav.hejny added 1 commit 2025-11-23 00:02:04 +00:00

feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 2 that supports DataResponse with file. 0528a20579

stanislav.hejny added 1 commit 2025-11-23 11:11:52 +00:00

feat/#89: Remove the warnings fund during pytest run b06e9a1f10

stanislav.hejny added 1 commit 2025-11-23 12:04:23 +00:00

feat/#89: Add test script to try all otdemo frontend endpoints 557a0fd756

stanislav.hejny added 1 commit 2025-11-23 12:25:13 +00:00

feat/#89: rename the test script because it is not unit test file daaf60ecbf

stanislav.hejny changed title from WIP: feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. to feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. 2025-11-23 13:00:36 +00:00

stanislav.hejny requested review from hurui200320 2025-11-23 13:00:44 +00:00

stanislav.hejny added this to the V.01 milestone 2025-11-23 13:00:47 +00:00

stanislav.hejny added this to the Sprint Nov 15- 28th project 2025-11-23 13:00:55 +00:00

hurui200320 added 1 commit 2025-11-24 06:28:18 +00:00

ci: update java amq router docker image tag d2b863b3cd

hurui200320 added 1 commit 2025-11-24 07:22:43 +00:00

build: build python library for 0.3.0 76874dd1f0

hurui200320 force-pushed feat/89 from 76874dd1f0 to d84a9f9fde 2025-11-24 07:23:26 +00:00 Compare

hurui200320 added 1 commit 2025-11-24 07:29:37 +00:00

ci: update cleverswarm lite docker image tag f3b7b279d3

hurui200320 approved these changes 2025-11-24 09:13:44 +00:00

hurui200320 left a comment

Member

Copy link

The code looks good to me. Although the pipeline is failing, but Stan and I have already figured out the issue and fix for the pipeline. It's outside of this repo (the fix should be impl in cleverswarm-lite), so I will approve this PR. After Stan fixed the issue and update the pipeline and everything passes, this PR should be good to go.

The code looks good to me. Although the pipeline is failing, but Stan and I have already figured out the issue and fix for the pipeline. It's outside of this repo (the fix should be impl in cleverswarm-lite), so I will approve this PR. After Stan fixed the issue and update the pipeline and everything passes, this PR should be good to go.

stanislav.hejny added 1 commit 2025-11-24 09:51:47 +00:00

feat/#89: Update CleverSwarm-lite image tag to fix bug associated with access to base64 payload that comes with AMQ Adapter v0.3.0 0bf302c914

stanislav.hejny merged commit fe0d23716a into develop 2025-11-24 13:47:36 +00:00

stanislav.hejny referenced this pull request from a commit 2025-11-24 13:47:37 +00:00

feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. (#113)

stanislav.hejny deleted branch feat/89 2025-11-24 13:47:52 +00:00

hurui200320 referenced this pull request from a commit 2025-11-28 05:55:18 +00:00

feat/#89: Implement File streaming protocol to support all addressing modes both on send and receive. Phase 1 that passes unit tests. (#113)

Sign in to join this conversation.

Reviewers

No reviewers

hurui200320

Labels

Clear labels

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

V.01

Projects

Clear projects

No items

No project

Sprint Nov 15- 28th

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

clevermicro/amq-adapter-python!113

No description provided.