Streamparse

Latest version: v4.1.2

Safety actively analyzes 629959 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

3.4.0

This release fixes a few bugs and adds a few new features that require pystorm 3.1.0 or greater.

Features
- Added a `ReliableSpout` implementation that can be used to have spouts that will automatically replay failed tuples up to a specified number of times before giving up on them. (pystorm/pystorm39)
- Added `Spout.activate` and `Spout.deactivate` methods that will be called in Storm 1.1.0 and above when a spout is activated or deactivated. This is handy if you want to close database connections on deactivation and reconnect on activation. (Issue 351, PR pystorm/pystorm42)
- Can now override `config.json` Nimbus host and port with the `STREAMPARSE_NIMBUS` environment variable (PR 347)
- Original topology name will now be sent to Storm as `topology.original_name` even when you're using `sparse --override_name`. (PR 354)

Fixes
- Fixed an issue where batching bolts would fail all batches they had received when they encountered an exception, even when `exit_on_exception` was `False`. Now they will only fail the current batch when `exit_on_exception` is `False`; if it is `True`, all batches are still failed. (PR pystorm/pystorm43)
- No longer call `lein jar` twice when creating jars. (PR 348)
- We now use `yaml.safe_load` instead of `yaml.load` when parsing command line options. (commit 6e8c4d8)

3.3.0

This release fixes a few bugs and adds the ability to pre-build JARs for submission to Storm/Nimbus..

Features
- Added `--local_jar_path` and `--remote_jar_path` options to `submit` to allow the re-use of pre-built JARs. This should make deploying topologies that are all within the same Python project much faster. (Issue 332)
- Added `help` subcommand, since it's not immediately obvious to users that `sparse -h submit` and `sparse submit -h` will return different help messages. (Issue 334)
- We now provide a universal wheel on PyPI (commit f600c98)
- `sparse kill` can now kill any topology and not just those that have a definition in your `topologies` folder. (commit 66b3a70)

Fixes
- Fixed Python 3 compatibility issue in `sparse stats` (Issue 333) an issue where `name` was being used instead of `override_name` when calling pre- and post-submit hooks. (10e8ce3)
- `sparse` will no longer hang without any indication of why when you run it as `root`. (Issue 324)
- RedisWordCount example topology works again (PR 336)
- Fix an issue where updating virtualenvs could be slow because certain versions of fabric would choke on the pip output (commit 9b1978f)

3.2.0

This release adds tools to simplify some common deployment scenarios where you need to deploy the same topology to different environments.

Features
- The `par` parameter for the `Component.spec()` method used to set options for components within your topology can now take dictionaries in addition to integers. The keys must be names of environments in your `config.json`, and the values are integers as before. This allows you to specify different parallelism hints for components depending on the environment they are deployed to. This is very helpful when one of your environments has more processing power than the other. (PR 326)
- Added `--requirements` options to `sparse update_virtualenv` and `sparse submit` commands so that you can customize the requirements files that are used for your virtualenv, instead of relying on files in your `virtualenv_specs` directory. (PR 328)
- pip is now automatically upgraded to 9.x on the worker nodes and is now run with the flags `--upgrade --upgrade-strategy only-if-needed` to ensure that requirements specified as ranges are upgraded to the same version on all machines, without needlessly upgrading all recursive dependencies. (PR 327)

Fixes
- Fixed an issue where `name` was being used instead of `override_name` when calling pre- and post-submit hooks. (10e8ce3)
- Docs have been updated to fix some RST rendering issues (issue 321)
- Updated quickstart to clarify which version of Storm is required (PR 315)
- Added information about flux-core dependency to help string for `sparse run` (PR 316)

3.1.1

This bugfix release fixes an issue where not having `graphviz` installed in your virtualenv would cause every command to crash, not just `sparse visualize` (311)

3.1.0

**Implemented enhancements:**
- Added `sparse visualize` command that will use graphviz to generate a visualization of your topology (PR 308)
![](https://www.dropbox.com/s/qv6v8o1s1eqdeo9/Screenshot%202016-08-31%2016.43.08.png?dl=1)
- Can now set ssh port in config.json (Issue 229, PR 309)
- Use latest Storm for quickstart (PR 306)
- Re-enable support for bolts without outputs in `sparse run` (PR 292)

**Fixed bugs:**
- `sparse run` error if more than one environment in config.json (Issue 304, PR 305)
- Switch from invoke to fabric for kafka-jvm to fix `TypeError` (Issue 301, PR 310)
- Rely on pystorm 3.0.3 to fix nested exception issue
- Updated bootstrap filter so that generated `project.clj` will work fine with both `sparse run` and `sparse submit`

3.0.1

Fixes an issue where `sparse submit` would crash if `log.path` was not set in `config.json` (Issue 293)

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.