Hello Gooddata team,
We want to know what is the ...
# gooddata-cns
Sunil Kumar Vanapalli
05/07/2024, 9:39 PMHello Gooddata team,
We want to know what is the difference of the errors in case of two different scenarios we query the data using attributes. This is what we see in logs and want to know the exact scenario these errors will be thrown to handle them accordingly. We have vague idea on when the AntiChain errors comes into picture where we query with unrelated attributes but
Genera errorA result cache error has occurred during the calculation of the resultProcessError(errorType=CLIENT_EXCEPTION, message=Antichain='[attribute/Account_StartDate.day/workspace_id, attribute/FinancialInstrumentTypeCode/workspace_id, attribute/GLActivity_AsOfDate.year/workspace_id, attribute/Transaction.AccountKey/workspace_id]' has no witness)A result cache error has occurred during the calculation of the resultProcessError(errorType=CLIENT_EXCEPTION, message=General error)i
Ivana Gasparekova
05/09/2024, 11:13 AMHi Sunil Kumar,
Your assumption is quite correct. You can find more details in this post. Iād suggest to use the validObjects API here as well.
The second error is quite generic, can you share more details with us, please?
What exactly let do this issue, please? Were you simply trying to render existing Insight, or were you adding a new attribute to your analytics?
s
Sunil Kumar Vanapalli
05/13/2024, 6:19 PMSorry for the late response, I missed your reply. I was trying to analyze with new attributes and measure combinations and got this error. I just want to know in what scenarios this error is thrown or else this error is a catch all and will be thrown for any sort of unhandled errors?
j
James Lee
05/13/2024, 6:22 PMthis is the error message for my recent query
James Lee
05/13/2024, 6:23 PMthe query is to fetch the following attributes:
[
{
"id": "AccountId"
},
{
"id": "FinancialInstrumentRealEstate.TenantClientOrgId"
},
{
"id": "FinancialInstrumentId"
},
{
"id": "Account.SourceAccountId"
}
]
s
Sunil Kumar Vanapalli
05/13/2024, 6:23 PMCan you share the LDM model for the attributes you selected @James Lee? that way Ivana can explain in what usecase this can happen
Sunil Kumar Vanapalli
05/13/2024, 6:24 PMI think in the above case there is a witness available
j
James Lee
05/15/2024, 8:15 PMtheres no ldm model, the above are attributes and we pass no filter models to the query since we're testing the combination of attributes only
James Lee
05/15/2024, 8:17 PMsdk.tables.for_items(
workspace_id=workspace_id,
items=[Attribute(local_id=name, label=name), ...],
filters=[],
)
James Lee
05/15/2024, 8:17 PMsomething like that where we pass in 4 attributes to the items parameter for each of the 4 attribute ids mentioned above
m
Martin Burian
05/20/2024, 4:24 PMHave you tried to find the trace id / result id in logs? Maybe there will be other log with more details.
r
Radek Novacek
05/28/2024, 9:20 AMHi all, have you had a chance to look into Martin's recommendation above? š
s
Sunil Kumar Vanapalli
05/31/2024, 6:26 AM@Martin Burian sorry for the late response.. we did check it that time and that says General Error too is what I remember
r
Radek Novacek
06/03/2024, 9:17 AMHi Sunil, essentially yeah, the "general error" is the high level error that gets reported, however the reason Martin is asking is that usually, even these catch-all errors are only a result of a different component reporting a more specific error, coupled with an error code that gets interpreted into a "general error".
So often enough, digging down via trace ID should lead you to a more specific (or well, sometimes at least longer) error message to go by š
7 Views