10:55 a.m.
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!
7:02 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/searchisko-dev
--
Vlastimil Elias
Principal Software Engineer
jboss.org Development Team
7:06 a.m.
Is there any code re-use that Jason can do here?
On 25 Sep 2014, at 13:02, Vlastimil Elias <velias(a)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(a)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)
6:37 p.m.
Paul and I were talking about this earlier today, is there a reason we couldn't use
the strata search to find all articles and solutions for a product and fetch those
returned URLs? If we were to do this, we'd cut out all the middle work and go straight
from one system to the next. What are your thoughts?
----- Original Message -----
From: "Vlastimil Elias" <velias(a)redhat.com>
To: searchisko-dev(a)lists.jboss.org, "Paul Robinson"
<paul.robinson(a)redhat.com>
Sent: Thursday, September 25, 2014 6:02:05 AM
Subject: Re: [searchisko-dev] Reusing an indexer from a river
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/searchisko-dev
--
Vlastimil Elias
Principal Software Engineer
jboss.org Development Team
_______________________________________________
searchisko-dev mailing list
searchisko-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/searchisko-dev
3628
days inactive
3630
days old
searchisko-dev@lists.jboss.org
3 comments
3 participants
participants (3)
-
Jason Porter -
Paul Robinson -
Vlastimil Elias