Allow configuration with chunk size when streaming #14
Labels
No labels
Complexity/Higest
Complexity/High
Complexity/Low
Complexity/Lowest
Complexity/Normal
Importance/High
Importance/Highest
Importance/Low
Importance/Lowest
Importance/Normal
Kind/Bug
Kind/Documentation
Kind/Feature
Kind/Structure
OS/Linux
OS/MacOS
OS/Windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#12 Add export and import method for graph
linarphy/galaxy-graph
Reference
linarphy/galaxy-graph#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Can be done using a configuration file, an environment variable, or a cli argument, but there is no cli yet.
For now, Converter don’t know about chunk, only the example class MermaidConverter use it. Should I specify it in the base class ?
I think chunk size is a mandatory setting for the
Converterbase class:A stream is a flow of data. A
Graphcan only contain a discrete number of components. . If we suppose any creation ofGraphfrom a string (construction) is procedural and incremental, there must be a components (Node or Connection) which is the last one added in any constructedGraph. The last element is defined as the element that do not have an element after it. Meaning the content of the string after the element has to be checked (and read if it exists).To know the end of a flow of data, one has to wait for it. In Python, that means fetching N bytes of data until no data is retrieved. This N number has to be defined. It can be hardcoded (not modifiable easily) or a configurable value.
The live and dead memory of a system are the parameters that guide the value of this number. As multiple systems exist, with different live and dead memory, this number must be configurable.
I should make sure every subclass of
Converteruse this setting (even if they use a library to ease the implementation, they must use libraries that allow to set a configurable chunk size). If not set, then they could all use a different chunk size as different format may have different size expectation.