[
https://issues.apache.org/jira/browse/PHOENIX-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306825#comment-15306825
]
James Taylor commented on PHOENIX-1833:
---------------------------------------
Awesome, [~rvaleti] - thanks so much for the patch. Couple of questions:
- This is for supporting a CRON job that'll kick off the async index build,
right? It's not yet automatically initiating the first async build when the
index is created yet, right? If that's the case, would you mind attaching your
patch to PHOENIX-2950 instead, and we can leave this JIRA to kick off the async
build *only the first time* when an index is created (when the server-side
MetaDataEndPointImpl.createTable call is made for an index).
- Would you mind adding a few lines of text to
https://phoenix.apache.org/secondary_indexing.html#Index_Population? The source
of this page is secondary_indexing.md, a markdown page that lives in SVN as
described here: https://phoenix.apache.org/building_website.html. We'd be
interested solely in the user-level means of using your very nice CRON job.
What needs to be configured/setup for the user to leverage it?
> Optionally trigger MR job to build index automatically
> ------------------------------------------------------
>
> Key: PHOENIX-1833
> URL: https://issues.apache.org/jira/browse/PHOENIX-1833
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Ravi Kishore Valeti
> Fix For: 4.8.0
>
> Attachments: PHOENIX-1833-0.98.patch
>
>
> Follow on work from PHOENIX-1609. This is to have the Phoenix client
> automatically kick off the MR index build for the ASYNC case. We can put in
> behind a config option so that folks who'd rather start the MR job manually
> can still do so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
