[
https://issues.apache.org/jira/browse/LENS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Gahlaut updated LENS-467:
----------------------------------
Description:
In the developer meet dated March 28, 2015, scope of addition of new drivers
like elastic search was discussed. Drivers like elastic search driver may
retrieve data using programmatic APIs instead of HQL from underlying storage
systems. In such cases it will be an overhead on driver side to translate HQL
to inputs to be given to programmatic APIs. These drivers may not have join
scope as well. This jira is to discuss the scope of communicating an object
with following information to drivers:
(a) List of Select
(b) From
(c) List of Where (filters)
(d) List of Group By
(e) List of Having
(f) List of Joins (Optional)
Lens has already parsed cube query and is aware of above mentioned lists. If
lens can communicate these lists to drivers instead of HQL, it will save
drivers from parsing HQL.
There may be various things which we have to consider to achieve the same. This
jira is to discuss the same.
Drivers may communicate via driver configuration file whether they are
interested in HQL or a POJO composed of above lists and lens may call
corresponding APIs on drivers.
was:
In the developer meet dated March 28, 2015, scope of addition of new drivers
like elastic search was discussed. Drivers like elastic search driver may
retrieve data using programmatic APIs instead of HQL from underlying storage
systems. In such cases it will be an overhead on driver side to translate HQL
to inputs to be given to programmatic APIs. These drivers may not have join
scope as well. This jira is to discuss the scope of communicating an object
with following information to drivers:
(a) List of Select
(b) From
(c) List of Where (filters)
(d) List of Group By
(e) List of Having
(f) List of Joins (Optional)
Lens has already parsed cube query and is aware of above mentioned lists. If
lens can communicate these lists to drivers instead of HQL, it will save
drivers from parsing HQL.
There may be various things which we have to consider to achieve the same. This
jira is to discuss the same.
Drivers may communicate via driver configuration file whether they are
interested in HQL or a POJOs composed of above lists and lens may call
corresponding APIs on drivers.
> Adding using POJOs as another communication protocol between Lens and Drivers
> -----------------------------------------------------------------------------
>
> Key: LENS-467
> URL: https://issues.apache.org/jira/browse/LENS-467
> Project: Apache Lens
> Issue Type: New Feature
> Reporter: Himanshu Gahlaut
>
> In the developer meet dated March 28, 2015, scope of addition of new drivers
> like elastic search was discussed. Drivers like elastic search driver may
> retrieve data using programmatic APIs instead of HQL from underlying storage
> systems. In such cases it will be an overhead on driver side to translate HQL
> to inputs to be given to programmatic APIs. These drivers may not have join
> scope as well. This jira is to discuss the scope of communicating an object
> with following information to drivers:
> (a) List of Select
> (b) From
> (c) List of Where (filters)
> (d) List of Group By
> (e) List of Having
> (f) List of Joins (Optional)
> Lens has already parsed cube query and is aware of above mentioned lists. If
> lens can communicate these lists to drivers instead of HQL, it will save
> drivers from parsing HQL.
> There may be various things which we have to consider to achieve the same.
> This jira is to discuss the same.
> Drivers may communicate via driver configuration file whether they are
> interested in HQL or a POJO composed of above lists and lens may call
> corresponding APIs on drivers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
