Fixed
Status Update
Comments
jo...@google.com <jo...@google.com>
al...@gmail.com <al...@gmail.com> #2
I think it makes a perfect sense as a feature request and is indeed distinct from other issues you referenced. Thanks for filing!
jo...@google.com <jo...@google.com> #3
I have CCed stakeholders and leaving the feature request assigned to myself for now.
ar...@google.com <ar...@google.com>
sa...@google.com <sa...@google.com> #4
Thanks for accepting this request, having this would be fantastic in my opinion (and my team's)!
ki...@gmail.com <ki...@gmail.com> #5
RE:"Thanks for accepting this request": this is just being brought for consideration. Thanks again for filing the feature request.
al...@gmail.com <al...@gmail.com> #6
Any progress on this?
This request is similar tohttps://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.
This request is similar to
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.
ad...@google.com <ad...@google.com> #7
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.
Using aggregation views to optimize query performance and cost is a different use case than using MV as a workaround to ELT.
ar...@google.com <ar...@google.com>
sa...@google.com <sa...@google.com> #8
#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...
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...
al...@gmail.com <al...@gmail.com> #9
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....
Description
a description of the documentation issue
----------------------------------------
The variable "groupOwnerAddress" is declared as type InetAddress, but that's not the type returned by getHostAddress().
InetAddress groupOwnerAddress = info.groupOwnerAddress.getHostAddress());
getHostAddress() returns a String.
the URL for the page in which it exists
---------------------------------------
a copy of the text or code that contains the issue
---------------------------------------------------
Under the subheading "Connect to a Peer", there is this code snippet:
@Override
public void onConnectionInfoAvailable(final WifiP2pInfo info) {
// InetAddress from WifiP2pInfo struct.
InetAddress groupOwnerAddress = info.groupOwnerAddress.getHostAddress());
// After the group negotiation, we can determine the group owner.
if (info.groupFormed && info.isGroupOwner) {
// Do whatever tasks are specific to the group owner.
// One common case is creating a server thread and accepting
// incoming connections.
} else if (info.groupFormed) {
// The other device acts as the client. In this case,
// you'll want to create a client thread that connects to the group
// owner.
}
}
Please also note that there's a typo in that code: there's an extra ")" after getHostAddress()