◆ Apache Cassandra

Query JSON data column using Spark

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskQuery the 'event_details' JSON column in the 'user_activity' table for all events where…+
Query the 'event_details' JSON column in the 'user_activity' table for all events where 'action' is 'login' and 'device' is 'mobile'. I need this data for the security audit by end of day.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I give this to the fraud detection team, query the 'event_details' JSON column in…+
Before I give this to the fraud detection team, query the 'event_details' JSON column in 'user_activity' for all 'purchase' actions. Extract the 'item_id' and 'price' from the JSON and make it easy to see which purchases exceed $100, so they can quickly spot suspicious transactions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe marketing team wants to segment users based on a 'campaign_id' nested deep inside the…+
The marketing team needs specific data from a deeply nested JSON column, and I'm not sure the best way to extract it efficiently.
The marketing team wants to segment users based on a 'campaign_id' nested deep inside the 'preferences' JSON column in the 'user_profiles' table. I'm afraid of writing an inefficient query that will hog resources or miss some data. What's the most performant way to extract this deeply nested 'campaign_id' from the JSON column using Spark, and what are the common pitfalls I should avoid?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting stuck when querying complex JSON data columns, often leading to slow queries or…+
I'm constantly struggling with querying complex JSON data, leading to slow queries and frustrated stakeholders.
I keep getting stuck when querying complex JSON data columns, often leading to slow queries or incorrect results, and then I have to redo the work. What habit should I change to more effectively and efficiently query nested JSON data, especially when I need to extract specific fields or filter on them, so I can deliver accurate results faster?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.