AAAR Extract Error Invalid layout detected in input streams, rows to append have to be of identical structure
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2015 06:38 AM
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 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) : org.pentaho.di.core.exception.KettleException:
2015/11/04 17:18:09 - Append streams.0 - Invalid layout detected in input streams, rows to append have to be of identical structure
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - The name of field number 26 is not the same as in the first row received: you're mixing rows with different layout. Field [owner_id Integer] does not have the same name as field [instance_id Integer].
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.processRow(Append.java:95)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62)
2015/11/04 17:18:09 - Append streams.0 - at java.lang.Thread.run(Thread.java:745)
2015/11/04 17:18:09 - Append streams.0 - Caused by: org.pentaho.di.core.exception.KettleRowException:
2015/11/04 17:18:09 - Append streams.0 - The name of field number 26 is not the same as in the first row received: you're mixing rows with different layout. Field [owner_id Integer] does not have the same name as field [instance_id Integer].
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.step.BaseStep.safeModeChecking(BaseStep.java:2054)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.checkInputLayoutValid(Append.java:159)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.processRow(Append.java:93)
2015/11/04 17:18:09 - Append streams.0 - … 2 more
2015/11/04 17:18:09 - Append streams.0 - Finished processing (I=0, O=0, R=9, W=8, U=0, E=1)
Thank you for your kind help.
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 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) : org.pentaho.di.core.exception.KettleException:
2015/11/04 17:18:09 - Append streams.0 - Invalid layout detected in input streams, rows to append have to be of identical structure
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - The name of field number 26 is not the same as in the first row received: you're mixing rows with different layout. Field [owner_id Integer] does not have the same name as field [instance_id Integer].
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.processRow(Append.java:95)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62)
2015/11/04 17:18:09 - Append streams.0 - at java.lang.Thread.run(Thread.java:745)
2015/11/04 17:18:09 - Append streams.0 - Caused by: org.pentaho.di.core.exception.KettleRowException:
2015/11/04 17:18:09 - Append streams.0 - The name of field number 26 is not the same as in the first row received: you're mixing rows with different layout. Field [owner_id Integer] does not have the same name as field [instance_id Integer].
2015/11/04 17:18:09 - Append streams.0 -
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.step.BaseStep.safeModeChecking(BaseStep.java:2054)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.checkInputLayoutValid(Append.java:159)
2015/11/04 17:18:09 - Append streams.0 - at org.pentaho.di.trans.steps.append.Append.processRow(Append.java:93)
2015/11/04 17:18:09 - Append streams.0 - … 2 more
2015/11/04 17:18:09 - Append streams.0 - Finished processing (I=0, O=0, R=9, W=8, U=0, E=1)
Thank you for your kind help.
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2015 08:12 AM
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.
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-05-2015 11:37 PM
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...'>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.
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...'>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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2015 02:43 AM
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.
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.
