org.pentaho.di.core.exception.KettleException: The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths.

Pentaho BI Platform Tracking | Meelan Laxman | 7 months ago
  1. 0

    Got this error even if "Ignore missing path" is checked. In the JSON I have an entry for "tenant-alias" but not "clone-from-tenant-alias". This should not generate any error. This transformation works on 6.0 but not on 6.1 {quote} 2016/05/11 17:25:21 - Spoon - Transformation opened. 2016/05/11 17:25:21 - Spoon - Launching transformation [SimpleUseCase]... 2016/05/11 17:25:21 - Spoon - Started the transformation execution. 2016/05/11 17:25:21 - SimpleUseCase - Dispatching started for transformation [SimpleUseCase] 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths. 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : org.pentaho.di.core.exception.KettleException: 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths. 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.evalCombinedResult(FastJsonReader.java:212) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.parse(FastJsonReader.java:154) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.parseNextInputToRowSet(JsonInput.java:244) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.getOneOutputRow(JsonInput.java:310) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.processRow(JsonInput.java:107) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at java.lang.Thread.run(Thread.java:745) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - Finished processing (I=0, O=0, R=0, W=0, U=0, E=1) 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - Spoon - The transformation has finished!! 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - SimpleUseCase - Transformation detected one or more steps with errors. 2016/05/11 17:25:23 - SimpleUseCase - Transformation is killing the other steps! {quote}

    Pentaho BI Platform Tracking | 7 months ago | Meelan Laxman
    org.pentaho.di.core.exception.KettleException: The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths.
  2. 0

    Got this error even if "Ignore missing path" is checked. In the JSON I have an entry for "tenant-alias" but not "clone-from-tenant-alias". This should not generate any error. This transformation works on 6.0 but not on 6.1 {quote} 2016/05/11 17:25:21 - Spoon - Transformation opened. 2016/05/11 17:25:21 - Spoon - Launching transformation [SimpleUseCase]... 2016/05/11 17:25:21 - Spoon - Started the transformation execution. 2016/05/11 17:25:21 - SimpleUseCase - Dispatching started for transformation [SimpleUseCase] 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths. 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : org.pentaho.di.core.exception.KettleException: 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths. 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.evalCombinedResult(FastJsonReader.java:212) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.parse(FastJsonReader.java:154) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.parseNextInputToRowSet(JsonInput.java:244) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.getOneOutputRow(JsonInput.java:310) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.steps.jsoninput.JsonInput.processRow(JsonInput.java:107) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - at java.lang.Thread.run(Thread.java:745) 2016/05/11 17:25:23 - ji: Parse Manifest file.0 - Finished processing (I=0, O=0, R=0, W=0, U=0, E=1) 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - Spoon - The transformation has finished!! 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - SimpleUseCase - ERROR (version 6.1.0.1-196, build 1 from 2016-04-07 12.08.49 by buildguy) : Errors detected! 2016/05/11 17:25:23 - SimpleUseCase - Transformation detected one or more steps with errors. 2016/05/11 17:25:23 - SimpleUseCase - Transformation is killing the other steps! {quote}

    Pentaho BI Platform Tracking | 7 months ago | Meelan Laxman
    org.pentaho.di.core.exception.KettleException: The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths.
  3. 0

    Elastic to Postgres data migration fails in kettle

    Stack Overflow | 2 years ago | Marlon Abeykoon
    org.pentaho.di.core.exception.KettleException: The data structure is not the same inside the resource! We found 1000 values for json path [$..LoginSessionId], which is different that the number retourned for path [$.ResourceChangeInfo..ResourceCode] (9325 values). We MUST have the same number of values for all paths.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Spoon PDI Data Validator Error

    Stack Overflow | 2 years ago | Paul
    org.pentaho.di.core.exception.KettleException: Correct Group/Dashboard Assignment Correct Group/Dashboard Assignment
  6. 0

    Error al realizar una transformacion con postgresql - Open Business Intelligence

    redopenbi.com | 1 year ago
    org.pentaho.di.core.exception.KettleException: 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - Error batch inserting rows into table [ejecmensual]. 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - Errors encountered (first 10): 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - Batch entry 0 INSERT INTO transformationpentaho.ejecmensual (ano_eje, sec_ejec, pliego, ejecutora, sec_func, programa, prod_pry, act_ai_obra, funcion, division_func, grupo_func, meta, finalidad, unidad_medida, cantidad, departamento, provincia, distrito, origen, fuente_financ_agregada, fuente_financ, tipo_recurso, categ_gasto, tipo_transaccion, generica, subgenerica, subgenerica_det, especifica, especifica_det, presupuesto, modificacion, pim, m01, m02, m03, m04, m05, m06, m07, m08, m09, m10, m11, m12, total_prog, saldo, porcentaje) VALUES ( '2014',  '001309',  '050',  '001',  '0001',  '0035',  '3000603',  '5004399',  '17',  '054',  '0119',  '00001',  '0107477',  '00194',  '9.0',  '01',  '02',  '99',  NULL,  '1',  NULL,  NULL,  '5',  '2',  '3',  NULL,  NULL,  NULL,  NULL,  '3754.0',  '0.0',  '3754.0',  '190.0',  '600.0',  '0.0',  '630.0',  '77.5',  '658.5',  '0.0',  '0.0',  '0.0',  '0.0',  '0.0',  '0.0',  '2156.0',  '1598.0',  '57.43') was aborted.  Call getNextException to see the cause. 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - ERROR: column "sec_ejec" of relation "ejecmensual" does not exist 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 -   Position: 57 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - Error updating batch 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - Batch entry 0 INSERT INTO transformationpentaho.ejecmensual (ano_eje, sec_ejec, pliego, ejecutora, sec_func, programa, prod_pry, act_ai_obra, funcion, division_func, grupo_func, meta, finalidad, unidad_medida, cantidad, departamento, provincia, distrito, origen, fuente_financ_agregada, fuente_financ, tipo_recurso, categ_gasto, tipo_transaccion, generica, subgenerica, subgenerica_det, especifica, especifica_det, presupuesto, modificacion, pim, m01, m02, m03, m04, m05, m06, m07, m08, m09, m10, m11, m12, total_prog, saldo, porcentaje) VALUES ( '2014',  '001309',  '050',  '001',  '0001',  '0035',  '3000603',  '5004399',  '17',  '054',  '0119',  '00001',  '0107477',  '00194',  '9.0',  '01',  '02',  '99',  NULL,  '1',  NULL,  NULL,  '5',  '2',  '3',  NULL,  NULL,  NULL,  NULL,  '3754.0',  '0.0',  '3754.0',  '190.0',  '600.0',  '0.0',  '630.0',  '77.5',  '658.5',  '0.0',  '0.0',  '0.0',  '0.0',  '0.0',  '0.0',  '2156.0',  '1598.0',  '57.43') was aborted.  Call getNextException to see the cause. 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 - 2014/07/24 11:34:02 - Ejecucion Mensual Table output.0 -

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.pentaho.di.core.exception.KettleException

      The data structure is not the same inside the resource! We found 0 values for json path [$.test-comment], which is different that the number returned for path [$.cleanup] (1 values). We MUST have the same number of values for all paths.

      at org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.evalCombinedResult()
    2. org.pentaho.di
      RunThread.run
      1. org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.evalCombinedResult(FastJsonReader.java:212)
      2. org.pentaho.di.trans.steps.jsoninput.reader.FastJsonReader.parse(FastJsonReader.java:154)
      3. org.pentaho.di.trans.steps.jsoninput.JsonInput.parseNextInputToRowSet(JsonInput.java:244)
      4. org.pentaho.di.trans.steps.jsoninput.JsonInput.getOneOutputRow(JsonInput.java:310)
      5. org.pentaho.di.trans.steps.jsoninput.JsonInput.processRow(JsonInput.java:107)
      6. org.pentaho.di.trans.step.RunThread.run(RunThread.java:62)
      6 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame