You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Rajashekhar (JIRA)" <ji...@apache.org> on 2019/07/09 08:29:00 UTC
[jira] [Updated] (LENS-1545) Fixed a Bug and made changes for
PreparedQuery
[ https://issues.apache.org/jira/browse/LENS-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajashekhar updated LENS-1545:
------------------------------
Description:
Fixed following Issues in Lens for Azure Migrations
# Bug in Lens-Metastore for single fact granularity -- https://issues.apache.org/jira/browse/LENS-1544. Explaination: This had a special case for handling facts with one-update-period and multiple-update-periods. The case which handled one-update-period had a bug while generating the name of the hive table whole format is update_period-fact_name, the update_period was coming as null.
# JDBCDriver.java was invoking JDBC Driver while validating the prepared query, I don't need this functionality so blocking this via already existing config parameter JDBC_VALIDATE_THROUGH_PREPARE.
2a) Old Flow:
{code}
esitmate()
--- | --> validate
-----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
-----|--> prepareInternal()
----------------|--> rewrite -- Rewritting take place
{code}
2b) New Flow:
{code}
esitmate()
---| --> rewrite -- Rewritting take place
---| --> validate
-----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
-----|--> prepareInternal()
{code}
was:
Fixed following Issues in Lens for Azure Migrations
# Bug in Lens-Metastore for single fact granularity -- https://issues.apache.org/jira/browse/LENS-1544. Explaination: This had a special case for handling facts with one-update-period and multiple-update-periods. The case which handled one-update-period had a bug while generating the name of the hive table whole format is update_period-fact_name, the update_period was coming as null.
# JDBCDriver.java was invoking JDBC Driver while validating the prepared query, I don't need this functionality so blocking this via already existing config parameter JDBC_VALIDATE_THROUGH_PREPARE.
2a) Old Flow:
esitmate()
{code}
--- | --> validate
-----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
-----|--> prepareInternal()
----------------|--> rewrite -- Rewritting take place
{code}
2b) New Flow:
esitmate()
---| --> rewrite -- Rewritting take place
---| --> validate
-----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
-----|--> prepareInternal()
> Fixed a Bug and made changes for PreparedQuery
> ----------------------------------------------
>
> Key: LENS-1545
> URL: https://issues.apache.org/jira/browse/LENS-1545
> Project: Apache Lens
> Issue Type: Improvement
> Components: api, cube, server
> Reporter: Rajashekhar
> Assignee: Amareshwari Sriramadasu
> Priority: Major
>
> Fixed following Issues in Lens for Azure Migrations
> # Bug in Lens-Metastore for single fact granularity -- https://issues.apache.org/jira/browse/LENS-1544. Explaination: This had a special case for handling facts with one-update-period and multiple-update-periods. The case which handled one-update-period had a bug while generating the name of the hive table whole format is update_period-fact_name, the update_period was coming as null.
> # JDBCDriver.java was invoking JDBC Driver while validating the prepared query, I don't need this functionality so blocking this via already existing config parameter JDBC_VALIDATE_THROUGH_PREPARE.
> 2a) Old Flow:
> {code}
> esitmate()
> --- | --> validate
> -----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
> -----|--> prepareInternal()
> ----------------|--> rewrite -- Rewritting take place
> {code}
> 2b) New Flow:
> {code}
> esitmate()
> ---| --> rewrite -- Rewritting take place
> ---| --> validate
> -----| --> JDBC_VALIDATE_THROUGH_PREPARE condition to prepare through if condition
> -----|--> prepareInternal()
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)