apache spark
for data engineers
Why this scored 15
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 128
Is a broadcast variable shared across multiple concurrent Spark jobs?
Explains whether Spark broadcast variables are shared across concurrent jobs. · for data engineers
stackoverflowCoolingdata1h ago - 216
Why does --packages work with spark-submit, but spark.jars.packages does not work with SparkSession.builder?
Clarifying package handling avoids runtime errors in Spark-BigQuery pipelines. · for data engineers
stackoverflowSteadydevtools16d ago