topic Re: AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure in Alfresco Archive

AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure

gatsu2811 — Wed, 04 Nov 2015 11:38:29 GMT

Hi everyone,I'm having problem extracting data with this return error;2015/11/04 17:18:09 - Append streams.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Unexpected error2015/11/04 17:18:09 - Append streams.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-3

Re: AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure

fcorti — Wed, 04 Nov 2015 13:12:47 GMT

Hi,

Which Pentaho version and AAAR version are you using?
Which step of the extraction caused that error? (you can see it in the log)
I have never seen this problem and I'm curious to discover the reason. 🙂

I see you are using Alfresco CE 5.0.a.
This version is the first one and I know it could be a bug on that side.

Re: AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure

gatsu2811 — Fri, 06 Nov 2015 04:37:19 GMT

Thank you for your reply Mr. Corti.

Fyi, I am using Pentaho 5.4 CE and AAAR 3.1.

Actually, I experienced the exact error with <a href='https://forums.alfresco.com/forum/installation-upgrades-configuration-integration/business-reporting/alfresco-422-aaar'>this post</a>, but I manage to bypass the error when I altered url_cmis_suffix at AAAR_DataMart.dm_dim_alfresco table from /alfresco/api/-default-/cmis/versions/1.1/atom to /alfresco/service/cmis. I believe the incident happened at workflow stage, but I could not figure out which workflow has triggered the event.

I also attached the snippet from AAAR.log regarding this issue. Any advise will be appreciated.

Thank you.

Re: AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure

fcorti — Fri, 06 Nov 2015 07:43:01 GMT

Hi Gatsu,

Few days ago has been released the AAAR v4 with a complete redesign of the extraction jobs.
My first suggestion is to move to this latest release.
In the new release the workflow extraction is not changed too much but I suggest you to move on it in any case (you can download it from the marketplace exactly in the same way you downloaded the AAAR v3.1).

Second hint:
Taking a look at the log file, I confirm it is an issue on the workflow extraction.
If not interested in workflow analytics you can avoid to extract it, updating the AAAR_Extract script in the way described below:
http://fcorti.com/alfresco-audit-analysis-reporting/aaar-advanced-configurations/
[Extract only audits, only repository informations or both.]

Third hint:
I'm sure you are agree with me that the previous hints are not a solution but a workaround. 😉
I confirm this is the first time I hear about this issue so I'm very interested to investigate.
I would like to debug the issue in my development environment to be sure about the solution.
Would you please write me at fcorti at gmail dot com because I would like to solve your problem using your data as a use case (if possibile).

Cheers.