从hue或r查询时的不同结果

uz75evzq  于 2021-06-24  发布在  Hive
关注(0)|答案(0)|浏览(238)

我正试图从一个Hive数据库中提取一些数据。通常我会开发/测试关于色调的查询,当我可以快速编写它们时(自动完成等),然后测试以查看结果。然后我转到我的rstudio,复制查询并使用rjdbc运行它。
最近我发现了一个令人费解的结果。如果我对hue和r运行完全相同的查询,我会得到不同的结果(更具体地说,我从r得到的结果更少)。知道为什么吗?由于我现在时间很短,我无法创建一个可复制的示例(实际的查询复制到下面)。

  1. SELECT OT3.id_ot id_ot,
  2. AP2.ID_SGM ua_sgm,
  3. OT3.DATA_VENDA DATA_VENDA,
  4. res_ot.RESULT resultado,
  5. OT3.TECNOLOGY TECNOLOGY,
  6. res_ot.RAZAO1 RAZAO1,
  7. res_ot.RAZAO2 RAZAO2,
  8. OT3.PLC PLC,
  9. OT3.tap tap,
  10. OT3.pd pd,
  11. OT3.COMENTARIO COMENTARIO
  12. FROM
  13. (SELECT OT2.id_ot id_ot,
  14. OT2.ua_cod ua_cod,
  15. OT2.DATA_VENDA DATA_VENDA,
  16. OT2.CLOSE_REASON_ID CLOSE_REASON_ID,
  17. OT2.TECNOLOGY TECNOLOGY,
  18. OT2.DATA_OT DATA_OT,
  19. OT2.COMENTARIO COMENTARIO,
  20. OT2.PLC PLC,
  21. OT2.tap tap,
  22. OT2.pd pd,
  23. ROW_NUMBER() OVER (PARTITION BY OT2.id_ot
  24. ORDER BY OT2.DATA_VENDA DESC, OT2.DATA_OT DESC) AS ROW_NUMBER,
  25. ROW_NUMBER() OVER (PARTITION BY OT2.ua_cod, OT2.DATA_VENDA, OT2.TECNOLOGY
  26. ORDER BY OT2.DATA_OT DESC) AS ROW_NUMBER_2
  27. FROM
  28. (SELECT OT1.work_order_id id_ot,
  29. OT1.ua_cod ua_cod,
  30. cast(OT1.work_order_dat AS DATE) DATA_VENDA,
  31. OT1.CLOSE_REASON_ID CLOSE_REASON_ID,
  32. CASE
  33. WHEN OT1.techonology_dsc = 'FTTH' THEN 'FTTH'
  34. WHEN OT1.techonology_dsc = 'CABO' THEN 'HFC'
  35. END AS TECNOLOGY,
  36. cast(OT1.WORK_ORDER_REAL_END_DAT AS DATE) DATA_OT,
  37. OT1.PLC_COD PLC,
  38. OT1.Tap_dsc tap,
  39. OT1.pd_dsc pd,
  40. concat(OT1.comments_txt, OT1.cancelation_comment_txt) COMENTARIO
  41. FROM dev_ads_dw.f_work_order OT1
  42. INNER JOIN dev_ads_dw.e_work_order_type TYPE ON OT1.work_order_type_id = TYPE.work_order_type_id
  43. INNER JOIN dev_ads_dw.e_task_type TASK ON OT1.task_type_id = TASK.task_type_id
  44. LEFT JOIN wb_cobr.mp_historico HIST ON OT1.work_order_id = HIST.id_ot
  45. WHERE OT1.CLOSE_REASON_ID <> -1
  46. AND OT1.techonology_dsc IN ('FTTH',
  47. 'CABO')
  48. AND OT1.ua_cod IS NOT NULL
  49. AND OT1.CLICK_CLIENT_CLASSIF_DSC IN ('RESIDENCIAL',
  50. 'NORMAL/RESIDENCIAL')
  51. AND (TYPE.work_order_type_dsc LIKE '%Instalação%'
  52. OR TASK.task_type_dsc LIKE '%ALTERACAO_TECNOLOGIA%')
  53. AND HIST.id_ot IS NULL ) OT2) OT3
  54. INNER JOIN
  55. (SELECT DISTINCT AP1.access_point_id AP_ID,
  56. AP1.id_alojamento ID_SGM,
  57. cast(regexp_replace(concat('20', AP1.valid_from), '\\.', '-') AS DATE) ap_valid_from,
  58. cast(regexp_replace(concat('20', AP1.valid_to), '\\.', '-') AS DATE) ap_valid_to
  59. FROM wb_cobr.h_access_point AP1) AP2 ON OT3.ua_cod = AP2.AP_ID
  60. INNER JOIN
  61. (SELECT DISTINCT RES_OT_TEMP.CLOSE_REASON_ID CLOSE_REASON_ID,
  62. UPPER(RES_OT_TEMP.close_reason_hier_lvl_1_txt) RESULT,
  63. UPPER(RES_OT_TEMP.close_reason_hier_lvl_2_txt) RAZAO1,
  64. UPPER(RES_OT_TEMP.close_reason_hier_lvl_3_txt) RAZAO2
  65. FROM dev_ads_dw.e_close_reason RES_OT_TEMP
  66. WHERE cast(RES_OT_TEMP.valid_to AS DATE) > CURRENT_DATE() ) res_ot ON ot3.CLOSE_REASON_ID = res_ot.CLOSE_REASON_ID

暂无答案!

目前还没有任何答案,快来回答吧!

相关问题