Hive REGEXP_EXTRACT Returns Empty String, Not NULL, When No Match
0: jdbc:hive2:/// (car)> select regexp_extract('220 km/h', '\\b(\\d+)\\b', 1) as speed;
OK
+--------+
| speed |
+--------+
| 220 |
+--------+
0: jdbc:hive2:/// (car)> select regexp_extract('-', '\\b(\\d+)\\b', 1) as speed;
OK
+--------+
| speed |
+--------+
| |
+--------+Many sources claim the return value is NULL, but it’s actually an empty string.
The Trust Quotient (TQ)
TQ—aka the Trust Quotient—is gonna be a big deal for AI. It’ll measure how reliable an AI is, whether it takes responsibility, and how well it fixes mistakes. And get this: in the future, when humans and AI work together, trust might matter even more than raw intelligence. TQ could end up deciding whether an AI gets trusted or gets access to key services.
Faster Rust builds on Mac
So, on Mac, when you build Rust projects (or any compiled code), sometimes the build scripts take way too long.
The author noticed this on their Mac, and it was weird because the same scripts run super fast on Linux. On Mac, each one took 0.5 to 3+ seconds, and each one was slower than the last. That doesn’t make sense — they’re just checking things like the Rust version.
After some digging, it turns out macOS has a security feature called XProtect. It scans every executable (like a build script) for malware — especially when it’s first launched or when the file changes.
So, every time a build script runs, macOS checks it for malware. That’s slow, especially if you have many scripts running one after another. It’s like having a security guard check every single file you create — even if it’s just a simple “check version” script.
The fix? You can tell macOS not to do this scan by adding your terminal (like Terminal or iTerm) to the list of developer tools in System Settings. After that, the build scripts run in under 0.1 seconds — a huge improvement.
Now, here’s the thing: this only helps if you’re building or testing things a lot.
If you just edit and rebuild code (like
cargo run), you’ll pay the delay every time.But if you run
cargo test, it’s a huge win — especially since some tests create thousands of tiny binaries. One test suite for the Rust compiler went from 9 minutes to 3 minutes just by disabling this scan.
The article says this is a hidden Mac behavior — most people don’t know about it. There’s a PR in Cargo (the Rust tool) that would warn users when XProtect is on, so they know it’s slowing things down. It’s a good idea because it helps users see a real performance problem they didn’t know existed.
Bottom line: If you’re on Mac and you do a lot of Rust testing or building, try turning off XProtect in your terminal settings — it can make builds and tests much faster, especially for testing. Just remember: you’re disabling a security feature, so only do it if you’re okay with that trade-off.
(And yeah, it’s not just Rust — any compiled language (C, C++, Go, Swift, etc.) might benefit too, if you’re compiling a lot.)