Forum Replies Created

  • csilvarivera

    Member
    February 15, 2024 at 12:00 am in reply to: BigQuery API no longer working

    Thank you Megan!

     

    FYI – the amazing support team has already given me a way forward. We just simply need to change the way we assign the default ProjectID as follows

     

     

    .com_kx_bq.cfg.default[`$"+projectId"]:"<PROJECTID>"

     

    And that’s pretty much it!  Not sure if the docs will be updated or a new version of the library will be released, but for now this works well.

  • csilvarivera

    Member
    February 12, 2024 at 12:00 am in reply to: BigQuery API no longer working

    Adding to the above. It is definitively an issue related to adding args in the run function. Executing a function that doesn’t require any args (i.e. list projects)  still works:

     

    q).com_kx_bq.projects.list[] kind | "bigquery#projectList" etag | "PXl7AcbMGzFMur/boIkUvA==" projects | +`kind`id`numericId`projectReference`friendlyName!(,"bigquery#pro.. totalItems| 1f

     

    I have added the default projectId in the configuration but no luck when trying to run any simple query or list datasets for example:

     

     

    .com_kx_bq.query "WITH AllTrades AS( SELECT * from project.dataset.demo)" 'Missing args, jobs.query requires args: +projectId [11] (.com_kx_bq.run) [10] (.com_kx_bq.queryRawResp)