[ 
https://issues.apache.org/jira/browse/HIVE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-15205:
------------------------------------
    Description: 
-- The current bootstrap code generates dump metadata during semantic analysis 
which breaks security and task/work abstraction. It also uses existing classes 
(from Export/Import world) for code reuse purpose, but as a result ends up 
dealing with a lot if-then-elses. It makes sense to have a cleaner abstraction 
which uses ReplDumpTask and ReplDumpWork (to configure the Task). Also perhaps 
worth evaluating ReplLoadTask/ReplLoadWork for load side.

-- Also consider including here: avoid deserializing notification and 
serializing again during repl dump. The notification should contain all info 
already (if not, fix it)

  was:The current bootstrap code generates dump metadata during semantic 
analysis which breaks security and task/work abstraction. It also uses existing 
classes (from Export/Import world) for code reuse purpose, but as a result ends 
up dealing with a lot if-then-elses. It makes sense to have a cleaner 
abstraction which uses ReplDumpTask and ReplDumpWork (to configure the Task). 
Also perhaps worth evaluating ReplLoadTask/ReplLoadWork for load side.


> Create ReplDumpTask/ReplDumpWork for dumping out metadata
> ---------------------------------------------------------
>
>                 Key: HIVE-15205
>                 URL: https://issues.apache.org/jira/browse/HIVE-15205
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>
> -- The current bootstrap code generates dump metadata during semantic 
> analysis which breaks security and task/work abstraction. It also uses 
> existing classes (from Export/Import world) for code reuse purpose, but as a 
> result ends up dealing with a lot if-then-elses. It makes sense to have a 
> cleaner abstraction which uses ReplDumpTask and ReplDumpWork (to configure 
> the Task). Also perhaps worth evaluating ReplLoadTask/ReplLoadWork for load 
> side.
> -- Also consider including here: avoid deserializing notification and 
> serializing again during repl dump. The notification should contain all info 
> already (if not, fix it)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to