Hi,

Thank you for your valuable suggestion and good to know that federated
tables are really views.

I had tried Dan's suggested method earlier, in that case, it was working
fine.  So what I infer from here we can't read federated tables directly in
Apache Beam. Please correct if I am wrong.

Regards,
Prabeesh K.

On 19 May 2017 at 02:28, Dan Halperin <[email protected]> wrote:

> Hi Prabeesh,
>
> I believe to read from a sheet you have to use a fromQuery("SELECT * FROM
> [sheet]"). This is because federated tables are really views and cannot be
> exported to GCS directly.
>
> On Thu, May 18, 2017 at 6:18 PM, Chamikara Jayalath <[email protected]>
> wrote:
>
>> I haven't tried reading BQ tables backed by Google sheets but this error
>> seems to be coming from BigQuery. Could you try contacting BQ support
>> channels ?
>>
>> Thanks,
>> Cham
>>
>> On Thu, May 18, 2017 at 5:26 AM Prabeesh K. <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> while I am trying to query the table that is backed by google sheet in
>>> beam python sdk getting following error. error(s): errorResult: Using
>>> table <table_name> is not allowed for this operation because of its type.
>>> Try using a different table that is of type TABLE., error: Using table
>>> <table_name> is not allowed for this operation because of its type. Try
>>> using a different table that is of type TABLE.
>>>
>>> Anybody help to fix this issue.
>>>
>>> Regards,
>>> Parbeesh K.
>>>
>>> On 5 May 2017 at 13:05, Prabeesh K. <[email protected]> wrote:
>>>
>>>> Hi Davor,
>>>>
>>>> Thank for your prompt reply.
>>>>
>>>> Regards,
>>>> Prabeesh K.
>>>>
>>>> On 5 May 2017 at 05:48, Davor Bonaci <[email protected]> wrote:
>>>>
>>>>> This sounds like a Dataflow-specific question, so it might be better
>>>>> addressed by a StackOverflow question tagged with google-cloud-dataflow 
>>>>> [1].
>>>>>
>>>>> I'd suggest checking the Dataflow documentation for more information
>>>>> about its security model [2]. You'd likely have to use a service account,
>>>>> as described there for a few scenarios.
>>>>>
>>>>> Hope this helps, but please don't hesitate to post on StackOverflow
>>>>> for any Dataflow-specific questions.
>>>>>
>>>>> Davor
>>>>>
>>>>> [1] http://stackoverflow.com/questions/tagged/google-cloud-dataflow
>>>>> [2] https://cloud.google.com/dataflow/security-and-permissions
>>>>>
>>>>> On Wed, May 3, 2017 at 11:08 PM, Prabeesh K. <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi Anil,
>>>>>>
>>>>>> Thank you for your attempt to answer the question. This is the broad
>>>>>> answer.
>>>>>>
>>>>>> The problem is we should add additional scope to Beam to read google
>>>>>> sheet and add the permission to the service account to read the google
>>>>>> sheet.
>>>>>>
>>>>>> Regards,
>>>>>> Prabeesh K.
>>>>>>
>>>>>>
>>>>>> On 4 May 2017 at 08:58, Anil Srinivas <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> The problem with it as what I see is that you don't have the
>>>>>>> permissions to access the data in the BigQuery table. Make sure you 
>>>>>>> login
>>>>>>> into the account which has permissions for reading/writing data in the
>>>>>>> table.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Anil
>>>>>>>
>>>>>>>
>>>>>>> On Wed, May 3, 2017 at 6:21 PM, Prabeesh K. <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> How to we can read a BigQuery table that backed by google sheet?
>>>>>>>>
>>>>>>>> For me, I am getting the following error.
>>>>>>>>
>>>>>>>> "error": {
>>>>>>>>   "errors": [
>>>>>>>>    {
>>>>>>>>     "domain": "global",
>>>>>>>>     "reason": "accessDenied",
>>>>>>>>     "message": "Access Denied: BigQuery BigQuery: Permission denied
>>>>>>>> while globbing file pattern.",
>>>>>>>>     "locationType": "other",
>>>>>>>>     "location": "/gdrive/id/------------------"
>>>>>>>>    }
>>>>>>>>   ],
>>>>>>>>   "code": 403,
>>>>>>>>   "message": "Access Denied: BigQuery BigQuery: Permission denied
>>>>>>>> while globbing file pattern."
>>>>>>>>  }
>>>>>>>> }
>>>>>>>>
>>>>>>>>
>>>>>>>> Help to fix this issue.
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Prabeesh K.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>

Reply via email to