Aperture REST API calls as Datasets within Aperture

13»

Answers

  • Henry Simms
    Henry Simms Administrator

    Hi @Marco_13112001 , I think it's likely that an error is being written to the Data Studio app log (datastudio.log) at the point when you're trying to view the rows. Could you check and let me know what the error is if you find one?

  • Marco_13112001
    Marco_13112001 Member
    edited April 3

    Hi @Henry Simms, see below also I've the attached the log extraction related with the error.

    2025-04-03 07:56:05,943 ERROR c.e.d.c.e.ErrorLogger [workpool-server-lowmem-executor-worker-8450] Error 66: 4009: Exception thrown by builder
    com.experian.datastudio.common.exceptions.ExecutionException: 4009: Exception thrown by builder
    at com.experian.datastudio.resource.ExecutorServiceBuilderWorkPool.maybeHandleException(ExecutorServiceBuilderWorkPool.java:385) ~[resource-2.16.2.jar:?]
    at com.experian.datastudio.resource.ExecutorServiceBuilderWorkPool.workBuilder(ExecutorServiceBuilderWorkPool.java:373) ~[resource-2.16.2.jar:?]
    at com.experian.datastudio.resource.ExecutorServiceBuilderWorkPool.lambda$new$0(ExecutorServiceBuilderWorkPool.java:114) ~[resource-2.16.2.jar:?]
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
    at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
    Caused by: java.io.IOException: java.sql.SQLException: [ApertureDataStudio][AutoREST JDBC Driver][AutoREST]REST Status 400 Bad Request returned for GET https://experian-dev.surreycc.local/api/1/datasets
    Caused by: com.experian.aperturedatastudio.jdbc.autorest.phoenix.api.core.aa: GET https://experian-dev.surreycc.local/api/1/datasets 400 Bad Request in statement [SELECT "ID","UUID","TYPE","NAME","SUMMARY","DESCRIPTION","EXTERNALLABEL","ENABLEDROPZONE","PUBLISHODATA","BATCHSETTINGS","BATCHLIMIT","ALLOWBATCHDELETION","ALLOWAUTOREFRESH","SPACENAME","SPACEID","SOURCE_SOURCETYPE","SOURCE_SYSTEM_ID","SOURCE_SYSTEM_UUID","SOURCE_SYSTEM_NAME","SOURCE_SYSTEM_DESCRIPTION","SOURCE_SYSTEM_TYPE","SOURCE_CREDENTIALS_ID","SOURCE_CREDENTIALS_UUID","SOURCE_CREDENTIALS_NAME" FROM "DATASETS"]
    at com.experian.datastudio.common.utility.IOUtils.toIOException(IOUtils.java:25) ~[common-2.16.2.jar:?]
    at com.experian.datastudio.datasource.connection.jdbc.JdbcSystemConnection.newRowIteratorCore(JdbcSystemConnection.java:769) ~[datasource-0.1.0.jar:?]
    at com.experian.datastudio.datasource.connection.jdbc.JdbcSystemConnection.newRowIterator(JdbcSystemConnection.java:727) ~[datasource-0.1.0.jar:?]
    at com.experian.datastudio.workflow.common.LoadDataUtils.lambda$loadDatasetBatches$1(LoadDataUtils.java:317) ~[workflowcommon-2.16.2.jar:?]
    at com.experian.datastudio.resource.loader.PooledDatasetLoader.hasWork(PooledDatasetLoader.java:186) ~[resource-2.16.2.jar:?]
    at com.experian.datastudio.resource.ExecutorServiceBuilderWorkPool.runWorkLoop(ExecutorServiceBuilderWorkPool.java:397) ~[resource-2.16.2.jar:?]
    at com.experian.datastudio.resource.ExecutorServiceBuilderWorkPool.workBuilder(ExecutorServiceBuilderWorkPool.java:356) ~[resource-2.16.2.jar:?]
    ... 6 more

    2025-04-03 075605,943 ERROR c.e.d.c.txt
  • Marco_13112001
    Marco_13112001 Member

    @Henry Simms I've isolated one the issues, please see below.

    [ApertureDataStudio][AutoREST JDBC Driver][AutoREST]REST Status 400 Bad Request returned for GET https://experian-dev.surreycc.local/api/1/datasets Caused by: com.experian.aperturedatastudio.jdbc.autorest.phoenix.api.core.aa: GET https://experian-dev.surreycc.local/api/1/datasets 400 Bad Request in statement [SELECT "ID","UUID","TYPE","NAME","SUMMARY","DESCRIPTION","EXTERNALLABEL","SPACENAME","SPACEID","SOURCE_SOURCETYPE","SOURCE_SYSTEM_ID","SOURCE_SYSTEM_UUID","SOURCE_SYSTEM_NAME","SOURCE_SYSTEM_DESCRIPTION","SOURCE_SYSTEM_TYPE","SOURCE_CREDENTIALS_ID","SOURCE_CREDENTIALS_UUID","SOURCE_CREDENTIALS_NAME" FROM "DATASETS"]

  • Marco_13112001
    Marco_13112001 Member

    @Henry Simms @Josh Boxer I've got the same issue when trying to retrieve a dataset list for our Development environment using Swager 'list of Dataset' endpoint. Is this an issue with our local setup configuration?

Categories