Infeasible
Status Update
Comments
we...@google.com <we...@google.com> #2
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ol...@gmail.com <ol...@gmail.com> #3
It's extremely frustrating that it's apparently now impossible on android 13 to write to data/obb without rooting devices. People hated this change in 11, hated it in 12, and now it's been done again. Please let us access the device we payed for. No one asked for this change.
jc...@google.com <jc...@google.com> #4
@3 It got even worse, as there is a bug that installer apps seem not to be able to do it anymore:
https://issuetracker.google.com/issues/254445476
ol...@gmail.com <ol...@gmail.com> #5
Extremely disappointing that google censored the original issue on this with over 2000 stars.
ol...@gmail.com <ol...@gmail.com> #6
Old issue was https://issuetracker.google.com/issues/196422354 and can't be accessed by the general public any more for some reason.
jc...@gmail.com <jc...@gmail.com> #7
Android/data No access to Debug File... Even as a Developer on a Non-Rooted Device. i just trying to make an App work again. but the Edits Need to Happen the Device even USB Debugging Prevents Write Access.. just Read...
if this Issue is not Resolved Soon. I will (I dont Know) but i paid over 1500.00 for a Device and i cant Access the Stuff i want.... and Articles that i used back A.11 Days are now Denied Access... KB196422354
Android 13 is a Joke if it Prevents People from Technical Experence from Doing what they want heck thats what the Developer Mode was For. now you have Bricked us again...
if this Issue is not Resolved Soon. I will (I dont Know) but i paid over 1500.00 for a Device and i cant Access the Stuff i want.... and Articles that i used back A.11 Days are now Denied Access... KB196422354
Android 13 is a Joke if it Prevents People from Technical Experence from Doing what they want heck thats what the Developer Mode was For. now you have Bricked us again...
Description
select
s.word
,sum(s2.word_count) over (partition by s.corpus) as count_corpus
,sum(s2.word_count) over () as count_total
from publicdata:samples.shakespeare s
inner join publicdata:samples.shakespeare s2
on s2.word = s.word
and s2.corpus = s.corpus
However, when I try to do this with our own tables, I am running into an unhelpful error message to the effect that the first field in the select statement cannot be found.
Job ID: snap-sale:job_SPeZfcVqIHlB0fzrsnAr7kcbhnY
I don't see any structural difference between these two queries, except that in the first query I am joining the table with itself.
Could you find out what causes this error, and if it cannot be fixed right away, change the error message into something less misleading?