IssueTracker

I think it makes a perfect sense as a feature request and is indeed distinct from other issues you referenced. Thanks for filing!

I have CCed stakeholders and leaving the feature request assigned to myself for now.

Thanks for accepting this request, having this would be fantastic in my opinion (and my team's)!

RE:"Thanks for accepting this request": this is just being brought for consideration. Thanks again for filing the feature request.

Any progress on this?
This request is similar to https://issuetracker.google.com/issues/72224267

Why are we so interested in this?

Our goal is to build an easy to maintain, basically 'NoETL' datawarehouse pipeline. Everywhere where we have to 'fall back' to Python programming makes the whole pipeline more complex to maintain. Having (parametrized) materialized views that could do a full or partial refresh would really be THE enabler for this.

Basically it would be something like Looker's Persistent Direived Tables, but then with the added abilities to:
-Refresh incrementally
-Fully use time partitioning and table suffixing.

What types of queries do you want to use in the MV?

Using aggregation views to optimize query performance and cost is a different use case than using MV as a workaround to ELT.

#7, for us the use cases would be both ETL and costs optimization queries (fyi, I am the original poster of these request)

IMO the main difference between the two patterns are:
1) ETL type MV's have more joins
2) Cost optimization MV's are simpler / aggregate style queries

In the end, what is important is that it supports the following refresh patterns:
1) easy: a full refresh (truncate / insert pattern). Oracle calls this a full refresh
2) more complex: incremental update, for this to work the insert/update/delete (or merge) has to be driven by a key. Oracle calls this the fast refresh option.

IMO this functionality could / should replace BQ scheduled queries, which I guess won't be a real focus anymore now that cloud composer is here...

Is there any progress with regards to this topic? Having materialised views in BigQuery would be the trigger for us to move away from our current solution, onto the BQ platform....

Tjeerd - please sync up with your Google Cloud account team to share roadmap under an NDA.

Is materialized view in early-access stage?
We just saw it in gcloud CLI and would like to try this feature.

How do we get access to the experimental materialized view feature?

please sync up with your Google Cloud account team to share roadmap under an NDA.

Had hoped something would be announced at Google Next '19, guess we'll have to wait :-(

Yep, would love this.

We are looking for this feature too, and it often comes up when we evaluate bq vs snowflake. Would be great if bq can support MVs.

with bq mk this is sort of possible (transfer jobs), something like:

bq mk \
--transfer_config \
--target_dataset='target_dataset' \
--display_name='schedule_name' \
--params='{"query":"SELECT xyz FROM table","destination_table_name_template":"target_table","write_disposition":"WRITE_APPEND"}' \
--data_source='scheduled_query' \
--schedule='every day 01:00'

nothing announced in Google Next 19 UK :(

was reading a blog about ML from google , and they dropped this info that materialized views are already in Alpha !!!!!!

Any update on this BQ team?  If it is in alpha, let us know ASAP!

are they still working on this? the issue is created on  "Jun 1, 2017 12:47PM" , But still can't see any update on Materialized view.

Another customer expressed interest in this capability.

Hi,

I have a customer that is very interested in joining early access for this functionality.
Can I help them by signing up somewhere?

Thanks,
Lorin

Ok, Good news, I asked the product manager of BigQuery in twitter, and he said, Google next 2020, which will be in a couple of weeks.

+1

+1

+1

We will announce support for materialized views in BQ soon. Stay tuned!

Beta available: https://cloud.google.com/bigquery/docs/materialized-views-best-practices

(emphasis on beta!)

Is there any scope to extend support to unnesting within the same table for MV's on the near horizon?

Thank you! Do you have reference/list of features to expect on V2?

Wow, even with the pixel 2XL this bug is long lasting.

El dic 4, 2017 6:31 PM, <buganizer-system@google.com> escribió:

how is this stilll a bug?

IKR. This annoys me soooo much. Especially in YouTube.

Still broken in pie. What a bummer

On Tue, Aug 7, 2018, 5:56 PM <buganizer-system@google.com> wrote:

Here is the explanation of why it will show up.  If you have a favorite app that uses accessibility see if the dev can make this update.  I fixed it on Signal Spy and everything seems to work great!

https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/volume/VolumeDialogImpl.java

computeFeedbackEnabled() shows that if there is any accessibility app that has any feedbackType other than 0 (none?) or FEEDBACK_GENERIC, then it will show for 20 seconds, otherwise 3.

What exactly do you mean by "I fixed it on Signal Spy and everything seems to work great?" I have the latest signal spy and still have the issue as of right now (OG Pixel, Android 9 Pie).

Yeah, Signal Spy still causes the issue for me too. Pixel XL, Android Pie.

How do we get this to be noticed? I just can't believe this is still a bug YEARS later and the status marked as fixed...

What version of Signal Spy?  The fix is in 1.9.9.6, if that doesn't fix it, send me an email at support@signalspy.com

I agree, this is absolutely nuts that it's been going on for so long and was classified as fixed even after they realized it was a problem. Signal Spy is my only accessabilty-enabled app, but I can imagine lots of people use other apps with accessabilty enabled.
To the Signal Spy guy/gal: I have 1.9.9.5, so that sounds promising, but I don't have an update available through the play store (I'm using the pro version). Any idea as to why/when it'll be available?

My fault, I thought I pushed it last night.  I just did it now, so to look for in the next few hours :)

Just updated Signal Spy, the issue is gone. Thank you

Hot shit! Finally fixed for me, thanks Signal Spy guy!! The issue remains for other apps, clearly, but now we have an app-by-app fix that sounds universal (thanks for nothing, Google)!

For me no change after update to 1.9.9.6, as I have other apps with accessibility enabled... So I'm assuming that the guy talking about pushing the signal spy update is the dev. Could you explain in layman's terms what exactly needs to be changed so other apps would/could be fixed as well?

I am the Signal Spy guy yes, nice to meet you :).  This article (https://www.xda-developers.com/why-android-phone-volume-dialog/) is by an XDA staffer who originally put me on to the solution and explains the issue very well.  You could also refer other devs to me and I would be glad to help, have them email me at support@novvia.com if so.

No not

I am having volume problems too