[ 
https://issues.apache.org/jira/browse/TAJO-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080622#comment-15080622
 ] 

ASF GitHub Bot commented on TAJO-2028:
--------------------------------------

Github user blrunner commented on a diff in the pull request:

    https://github.com/apache/tajo/pull/916#discussion_r48700968
  
    --- Diff: tajo-docs/src/main/sphinx/hive_integration.rst ---
    @@ -35,8 +41,8 @@ Finally, you should specify HiveCatalogStore as Tajo 
catalog driver class in ``c
       ``ALTER TABLE table_name ADD PARTITION`` commands on each of the newly 
added partitions or
       ``MSCK REPAIR TABLE  table_name`` command.
     
    -  But current tajo doesn't provide ``ADD PARTITION`` command and hive 
doesn't provide an api for
    -  responding to ``MSK REPAIR TABLE`` command. Thus, if you insert data to 
hive partitioned
    -  table and you want to scan the updated partitions through Tajo, you must 
run following command on hive ::
    +  But current Tajo doesn't provide ``ADD PARTITION`` command and Hive 
doesn't provide an api for
    +  responding to ``MSK REPAIR TABLE`` command. Thus, if you insert data to 
Hive partitioned
    +  table and you want to scan the updated partitions through Tajo, you must 
run following command on Hive:
     
    --- End diff --
    
    If you add ``.. code-block:: sh``, description below would be more clear. 


> Refining Hive Integration document including typo
> -------------------------------------------------
>
>                 Key: TAJO-2028
>                 URL: https://issues.apache.org/jira/browse/TAJO-2028
>             Project: Tajo
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Jongyoung Park
>            Assignee: Jongyoung Park
>            Priority: Minor
>             Fix For: 0.11.0
>
>
> Trivial typo was found in Hive Integration document.
> And, some modification is needed for better displaying.



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

Reply via email to