CEP-32: OpenTelemetry Tracing is coming to #ApacheCassandra! 🔍
Vote passed. Native OTel integration — correlate Cassandra query spans with your existing observability stack.
cwiki.apache.org/confluence/d...
#OpenTelemetry #NoSQL #Observability #OpenSource
[RELEASE] Apache Cassandra 6.0-alpha1 is out ‼️
This is a quarterly alpha release, for testing and development purposes.
Download it at: downloads.apache.org/cassandra/6....
News: github.com/apache/cassa...
Changelogs: github.com/apache/cassa...
„Over the next couple of years, the most valuable people to have on a software team are going to be experienced folks who’re actively working to keep their heuristics fresh. Who can combine curiosity with experience.“
buff.ly/HYgxmFn
#developer #leadership #AI
> hardwood print -f s3://user-agents/date=2026-03-27/part-00000-8d0eba93-ec09-4c48-95df-4b4145690664.c000.zstd.parquet -n 10
All the CLI tooling you expected to work with #parquet / #iceberg files is coming to life with #hardwood !
github.com/hardwood-hq/...
Congrats on the site revamping! (and the tool but I already knew this one ;)).
My modest attempt to make it easier to work with multistack and inconsistent #json logging formatters (#java, #dotnet, #go there)
-> github.com/yupiik/yuc/p...
kubectl logs whatever | yuc auto-logs
and enjoy :), no more headache to recall the jq pattern/syntax to use or switch between 5-6 aliases
Finally there is some specific UI for #openrpc a bit more advanced/usable than the default playground, no more need of the #swaggerui dirty hack (using path as method)
> octanolabs.github.io/d0x/#/etc
Still hoping @intellijidea.com gets support for #java #annotationprocessor with its incremental compilation optimization
> youtrack.jetbrains.com/issue/IDEA-3...
Really like the templating capability of last #maven dependency plugin, so easy to generate #asciidoc from your deps now!
living #doc with #maven is one more step easier
And another one
> github.com/dotnet/runti...
Who care about class or method names in logs?....seriously
#dotnet "common" logging scenario looks weird, the common need seems to not have anything usable when enabling single line
> github.com/dotnet/runti...
First JDK 26 Release Candidate: mail.openjdk.org/pipermail/jd...
Downloads: jdk.java.net/26/
#JDK26 #Java26 #OpenJDK #TestItNow
Well, best workaround is "-Dsurefire.enableProcessChecker=" or set it in the pom or leave it blank....this is actually no more needed since we have container based CI.
#dotnet tip:
> export MSBUILDTERMINALLOGGER=off
and you get back useful logs on dotnet commands
Testing your #java deployments (#bundlebee), upgrades, operator with #junit never had been so easy!
Fun fact, how to go faster than HTTP/2.0 on an API?
....
Using HTTP/1.1 :D
The story behind: being able to use the MAX_CONCURRENT_STREAMS value to respect it can be very challenging depending the lib you do use so 1.1 *can* be faster for you
Ce coup de gueule de Rob Pike (co-créateur de Go, et de l’UTF-8) sur l’IAGen est salutaire et rééquilibre l’ambiance positiviste et dépourvue de recul qui domine dans la communauté IT.
La dissonance cognitive n’est jamais confortable mais elle est souvent salvatrice…
yep (and fail the build if requested), guess you can write a jbang command to make it or workaround it with ejecting as a maven project (not sure it would be good but that's how I see it can work today)
say me ossindex plugin too and I can test it again (seriously)
I can but I literally don't get benefits but only drawbacks.
I can accept a few drawbacks if it becomes a one trivial command (x script.java) else I'd just go with #maven and keep the sane existing and shared ecosystem about vulnerability scanning, automatic upgrades etc...
maven is supported everywhere, trivial to setup
jbang requires some knowledge, plugins not working always very well (vscode integration is not great - not jbang plugin fault only, eclipse stack is to blame also) and is a new toy not that well known
so => it is negative since it doesnt make it better
FTR, being maven (or resolver) first is my current _default_ option and it works super well with plain java so jbang gain would be negative if I go that path
IDE is 80% about completion, if it can run it is great, if not console is fine I think. Challenge there is really completion only.
And if I need a whatever.build.file I'd just make it a pom.xml and be it, will work and be integrated everywhere.
Guess it will be only usable better once openjdk.org/jeps/468 pops up by default, but we're on track!
Yes, and do not get it wrong, it fails as the expectation of jbang to be better than literally "mvn" command in terms of work for the end users.
We're in IT, everything always works ;), it is just not as frictless as I expected there "everywhere"
I'd say it works for your case, for mine it breaks it and the gain I was hoping to move from either maven or 2 different commands to jbang is actually not there, so it doesn't for me but it is ok ;)
ack that, was trying to get a one liner to get started for non "native java" guys but using stdout can not be the best option even if the most convenient (in particular with the new IO class).
(following of previous answer - NotEnoughCharException ;)) issue is on env where you also assert stderr is clean for ran scripts only - and not only exit code. Same spirit than the old jenkins rule "no warning at all" if you recall this plugin.
not much a preference thing, it is literally that output must be yaml/json to be piped so it you start with logger lines you break it. Since quiet can't be in a directive it ends as being the script hacked on the shebang line or another script/file which defeats the whole jbang usage there
