Page History

...

• For interpreters which use SQL

• Keep the query to reproduce table result later

• Or create a view in the storage using the requested query

• For interpreters which use programming language

• Keep reference/info to RDD, Data Frame, or other variables in replREPL

• For interpreters which use DSL (e.g ElasticsearchInterpreter)

  • TBD

...

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

• ZEPPELIN-TBD: ResourceRegistry

• ZEPPELIN-TBD: Rest API for resource pool

• ZEPPELIN-TBD: UI for `Table` page

• ZEPPELIN_-TBD: Apply `pivot`, `filter` methods for built-in visualisations

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

• ZEPPELIN-2029: ACL for `ResourcePool`

• ZEPPELIN-2022: Zeppelin resource pool as Spark DataSource
  
  

...

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

• 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 pandas data frame using TableData

  Code Block
  language py linenumbers true
  # 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