...

• ZEPPELIN-753: added abstraction for tabledata

• ZEPPELIN-2020: implemented remote method invocation 

Based on these worksabove work, this proposal aims to build a mechanism for handling table resource in backend and design API for the resource pool. This will bring Zeppelin to 

...

For more future work tasks, please refer the 67. Potential Future Work section

...

The next paragraph execution, the resource will be updated if it has the same name.

6

...

. Roadmap

The issues we discussed above can be implemented in this sequence.

• ZEPPELIN-TBD: Adding `pivot`, `filter` to TableData

• ZEPPELIN-TBD: ResourceRegistry

• ZEPPELIN-TBD:

• ZEPPELIN-TBD: Rest API for resource pool

• ZEPPELIN-TBD: UI for `Table` page

• ZEPPELIN_TBD: Apply `pivot`, `filter` methods for built-in visualizations

• ZEPPELIN-TBD: SparkTableData, SparkSQLTableData, JDBCTableData, etc.

• ZEPPELIN-2029: ACL for `ResourcePool`

• ZEPPELIN-2022: Make SparkInterpreter directly access TableData in ResourcePoolUI for list / preview / download available resourcesZeppelin resource pool as Spark DataSource

7. Potential Future Work

• Watch / Unwatch: for automatic paragraph updating for Streaming Data Representation.

• ZEPPELIN-1494: Bind JDBC result to a dataset on the Zeppelin context

• Ability to construct table result from the resource pool in language interpreters (e.g python)

• Let’s assume that we can build a pandas dataframe using TableData

  Code Block
  language py
  # in python interpreter t = z.get("tableResourceName") # will return object that has `hasNext` and `next` p = new PandasTableData(t) # use p.pandasInstance …

   

   

• ZEPPELIN-1494: Bind JDBC result to a dataset on the Zeppelin context