Update developer documentation to reflect new compute_schema changes #1341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…kes 1.5m down from 5m
…rvice_fixture moved out of conftest
dagardner-nv
added
non-breaking
…ith MultiMessage however the Python impl accepts typing.Any. Re-work example to only use the C++ impl when the input type is a MultiMessage [no ci]
… first where the Python impl will be returned, the second where the C++ impl is returned [no ci]
…g the stage's unique name
…s to work with MessageMeta instances to make it easier to incorporate into a Morpheus pipeline [no ci]
drobison00
approved these changes
Nov 7, 2023
…avid-23.11-docs-1252
dagardner-nv
changed the title
|
/merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
compute_schemachanges.--run_milvusflag fromfea-sherlock(unrelated I just needed to quickly run the rest of the tests)examples/developer_guide/3_simple_cpp_stage/pass_thru.py, where the Python impl can support messages of any type, but the C++ impl only supportsMultiMessagedocs/source/developer_guide/guides/7_python_modules.mdintoexamples/developer_guide/7_python_modules/allowing them to be tested & validated. Add a simple end-to-end test for the modules & stages (part of [DOC]: Add code for module developer guides to examples/developer_guide #993)MessageMetarather thanintmaking it easier to run in a Morpheus pipeline.Closes #1252
By Submitting this PR I confirm: