• Sign In
  1. Messages

Query validation fails and API getSchema

LabKey Support Forum

View Message

view list print
Query validation fails and API getSchema christian opitz  2022-01-20 07:56
Status: Active
 

Following the upgrade to 21.11.4 (thanks to log4j), I am not able to retrieve a table called RunRepresentativeDataState for the targetedms schema via the Rlabkey package. getSchema throws the following Error: Status code = 404, Error message = Could not find the query

Funnily enough the table is contained in the data frame returned by getQueries. However, one cannot use getQueryDetails with this particular as expected.

Running the query validation within Labkey confirms this error with: targetedms.RunRepresentativeDataState: Query not found: RunRepresentativeDataState

Is there any remedy to this?

Thank you very much.
 
 
jeckels responded:  2022-01-21 16:47

Hi Christian,

Thanks for your report. I checked and there is indeed a metadata mismatch on this table. In some places the server is expecting the table name to be RunRepresentativeDataState and in others it's expecting it to be RepresentativeDataState_Run. The latter should work via the R API and other pathways so I recommend that approach.

Looking at the history of the code I can't any recent changes that would have impacted this, but it should be an easy to fix to reconcile them and have the server respond to either name in case there was a change that disconnected support for "RunRepresentativeDataState".

https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=44713

Thanks,
Josh
 
christian opitz responded:  2022-01-24 03:01

Hi Josh

Thank you for the timely reply. Seeing that you have already pushed a fix to repo, is it already part of the distributed zip file? So one can fix it by patching?

Otherwise I would need to change code to move away from query objects and explicitly call the schemas and views requested. I do not depend on the RunRepresentativeDataState at all but retrieving the entire object via getSchema() will yield the error.

Thanks again,
Christian
 
jeckels responded:  2022-01-25 10:30

Hi Christian,

We haven't yet rolled out a new maintenance release that includes this fix. Are you using PanoramaWeb.org or a separate deployment?

Thanks,
Josh
 
christian opitz responded:  2022-03-22 06:46

Dear Josh

I am very sorry for the late reply - a lot of things have been getting in my way. Thank you for following up.

We indeed use a separate instance. I have just seen the 22.3 that now comes without Panorama, which is a bummer. Is there any chance of having a revised 21.X to remediate the problem with the query meta tables?

Thanks a bucket,
Christian