Page History

...

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

• provide an interpreter option: create `TableData` TableData whenever executing a paragraph

• or provide new interpreter magic for it: `elasticserach %elasticserach_share

• or automatically put all table results into the resource pool if they are not heavy

...

• 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 REPL

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

  • TBD

5.3. What should the table name be?

...

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

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

• ZEPPELIN-TBD: ResourceRegistry

• ZEPPELIN-TBD: Rest API for resource pool

• ZEPPELIN-TBD: UI for `Table` page

• ZEPPELIN-TBD: Apply `pivot` pivot, `filter` filter methods for built-in visualisationsvisualizations

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

• ZEPPELIN-2029: ACL for `ResourcePool` ResourcePool

• ZEPPELIN-2022: Zeppelin resource pool as Spark DataSource
  
  

...