IssueTracker

Comment has been deleted.

I disagree that the new DECLARE syntax in scripting fully solves this problem.

If you have an existing parameterized query, the parameter names start with @. You cannot declare a variable that starts with @, so you would still need to modify the query body.

I would love to see a solution where I can take a copy and paste the unmodified text of a production query into the console and be able to run it with parameters set to specific values.

All +1 trolling aside,
Please do NOT close this thread, since there is still no option to specify query parameters in the userinterface, as the original request specified.

And for me, the workaround using scripting is not clear at all:

DECLARE foo STRING DEFAULT 'bar';
SELECT @foo;

Throws error:
Query error: Query parameter 'foo' not found at [2:8]

+1

I have been able to use parameters in the UI declaring them in the script.

A dummy example that uses parameters even to name the output table:

declare var_table_name  string        default 'test_contacts';
declare var_cities      array<string> default ['New York','Chicago','Boston']; # cities with 24h open stores

create temp table stores_details as

select
    city_id,
    phone_number
from stores
where city_name in unnest(var_cities);

execute immediate ('create or replace table '|| concat('schema.', var_table_name ) ||' as select * from stores_details');

To all affected customers, please note that the BigQuery engineering team is aware of this feature request, as well as its popularity, and any update on its progress will be given through this medium. Please consider that feature requests don't have any SLAs which means there is no specific time bound on when the request can be resolved/granted

That said, I strongly advice to avoid commenting "+1" without any further details. If you wish to express your support for this feature request, please click on the star button next to the issue name. I've attached a screenshot of where you can view this button on the top left corner.

This is the best way to inform the engineering team you are also affected by the issue. Otherwise your comment will be considered spam

Thank you.

Let me share just another tricky workaround for this: use BEGIN...EXCEPTION...END instead of EXECUTE IMMEDIATE.

declare v int64 default 123;
begin
  set v = @v;
exception when error then
  /* fallback to default */
end;
select v;

+1

So, the BigQuery engineering team is aware of the feature request but its technical implementation has not yet begun, right?

Correct, this has been discussed internally but we still not have an SLA to share.

For all our customer, if you are also interested in this feature, please "star" the ticket, there is no need to comment +1 as the best metric for the interest is the number of stars.

What is the status of this ticket?

This is clearly never going to happen, so Google should just close it, and get it over with.

Happy 9th birthday!

(and, un-accepting and un-assigning seems like moving in the wrong direction...)