[searchisko-dev] Reusing an indexer from a river

[Paul Robinson]

Is there any code re-use that Jason can do here? 

On 25 Sep 2014, at 13:02, Vlastimil Elias <velias at redhat.com> wrote:

> Hi Jason,
> 
> if I understand correctly, you can stop to use river running inside DCP
> for indexing articles and solutions from access.redhat.com, and start to
> push/delete this content directly from your side/build over REST API.
> 
> In this case you have to move content definition for these types from
> provider called 'rht' under you provider (jboss-developer). As we use
> naming conventions for ES index names it also means you have to create
> new indexes, but you are right that you can simply take current
> definitions and modify them.
> During deployment of your new definitions we also have to remove old
> 'rht' provider and both rivers related to it.
> 
> Cheers
> 
> Vlastimil
> 
> On 23.9.2014 17:55, Jason Porter wrote:
>> Hey all, we're looking at a better way for indexing articles and solutions from access.redhat.com. I'm wondering if we can reuse the river index for this, or if we need to create a new one. If we can copy and paste (and slightly modify) the current index that works too. Thanks!
>> _______________________________________________
>> searchisko-dev mailing list
>> searchisko-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/searchisko-dev
> 
> -- 
> Vlastimil Elias
> Principal Software Engineer
> jboss.org Development Team
> 
> 


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/searchisko-dev/attachments/20140925/ab75a5d6/attachment-0001.html