Comments (5)
from natscli.
You cannot make a stream with subjects “>”
that will ingest into it many unrelated messages, including as is happening here the API requests.
What you are seeing is the ACk that the API request was stored before the API response
you need to make streams with only just what you need.
from natscli.
@ripienaar I understand that the use of >
as a subject filter would create a stream that would ingest all messages. That was actually the intention.
If this should be considered an illegal operation the server should have rejected the command. The fact remains that under these circumstances a user can render the jetstream subcommands inoperable by running this command nats stream add BUG --subjects=">"
.
Would you please consider reopening this?
from natscli.
Will add a check. But successfully checking for any subject that can cause trouble is simply not possible as to a large extend it depends on your environment.
from natscli.
@ripienaar thank you!
This was a really awesome turn around time.
from natscli.
Related Issues (20)
- nats str edit cannot update Subject Transform HOT 2
- A bug that was filed in nats.go HOT 2
- If user is set then token is not transmitted HOT 2
- Displayed ObjectStore digest is truncated HOT 1
- Not recognizing difference in stream configuration for sources HOT 1
- Support wildcard for KV get HOT 11
- Broken nats-cli arm64 binary HOT 3
- Stream info shows first and last timestamps incorrectly HOT 2
- Enable inactive-threshold flag while editing consumer HOT 2
- Can't create pull consumer from cli HOT 10
- Extend --trace or add a --debug flag to see server connections HOT 2
- req: set exit status based on: response / header existing
- Incorrect local JetStream store directory when $XDG_DATA_HOME is defined HOT 1
- Change `--completion-script-bash` option to `completion bash` by convention
- Add support for the s390x architecture HOT 1
- Context subcommand "create" missing from CLI Menu HOT 2
- sub: allow multiple subjects HOT 1
- Consider making a new release HOT 2
- Upload of large object fails with `nats: error: nats: stalled with too many outstanding async published messages`
- Consumer pause/resume commands fail after selecting stream/consumer
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from natscli.