[jira] [Closed] (CAMEL-15269) How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
[ https://issues.apache.org/jira/browse/CAMEL-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino closed CAMEL-15269. > How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira > -- > > Key: CAMEL-15269 > URL: https://issues.apache.org/jira/browse/CAMEL-15269 > Project: Camel > Issue Type: Task > Components: camel-jira >Reporter: Daniel Caloto Suárez >Priority: Major > > Hello > I'm new to kafka. I would like to know how to install the > CAMEL-JIRA-KAFKA-CONNECTOR and how to configure it. > Where do I have to put the unit > > org.apache.camel.kafkaconnector > camel-jira-kafka-connector > x.x.x > > > Where to extract the file > camel-jira-kafka-connector-0.3.0-package.tar.gz > Where and how to set options such as > camel.source.endpoint.jql > Thank you very much for everything > Dani -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15269) How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
[ https://issues.apache.org/jira/browse/CAMEL-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15269. -- Resolution: Invalid > How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira > -- > > Key: CAMEL-15269 > URL: https://issues.apache.org/jira/browse/CAMEL-15269 > Project: Camel > Issue Type: Task > Components: camel-jira >Reporter: Daniel Caloto Suárez >Priority: Major > > Hello > I'm new to kafka. I would like to know how to install the > CAMEL-JIRA-KAFKA-CONNECTOR and how to configure it. > Where do I have to put the unit > > org.apache.camel.kafkaconnector > camel-jira-kafka-connector > x.x.x > > > Where to extract the file > camel-jira-kafka-connector-0.3.0-package.tar.gz > Where and how to set options such as > camel.source.endpoint.jql > Thank you very much for everything > Dani -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15269) How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
[ https://issues.apache.org/jira/browse/CAMEL-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152511#comment-17152511 ] Andrea Cosentino commented on CAMEL-15269: -- Please, open the issue in the camel-kafka-connector issue tracker. [https://github.com/apache/camel-kafka-connector] This is the issue tracker for pure camel. > How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira > -- > > Key: CAMEL-15269 > URL: https://issues.apache.org/jira/browse/CAMEL-15269 > Project: Camel > Issue Type: Task > Components: camel-jira >Reporter: Daniel Caloto Suárez >Priority: Major > > Hello > I'm new to kafka. I would like to know how to install the > CAMEL-JIRA-KAFKA-CONNECTOR and how to configure it. > Where do I have to put the unit > > org.apache.camel.kafkaconnector > camel-jira-kafka-connector > x.x.x > > > Where to extract the file > camel-jira-kafka-connector-0.3.0-package.tar.gz > Where and how to set options such as > camel.source.endpoint.jql > Thank you very much for everything > Dani -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15269) How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
[
https://issues.apache.org/jira/browse/CAMEL-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152506#comment-17152506
]
Thomas edited comment on CAMEL-15269 at 7/7/20, 6:28 AM:
-
Hi guys
I am also struggling with the same issue. I followed the provided documentation
and took the configuration base from the projects example.
I always run into the following error:
{code:java}
[2020-07-07 00:12:11,684] ERROR WorkerSourceTask{id=CamelJiraSourceConnector-0}
Task threw an uncaught and unrecoverable exception
(org.apache.kafka.connect.runtime.WorkerTask:186)
org.apache.kafka.connect.errors.ConnectException: Failed to create and start
Camel context
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:103)
at
org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:213)
at
org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:184)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:234)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: Cannot find endpoint with scheme
jira
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.doAsEndpointUri(AbstractCamelCatalog.java:684)
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.asEndpointUri(AbstractCamelCatalog.java:673)
at
org.apache.camel.kafkaconnector.utils.TaskHelper.buildUrl(TaskHelper.java:44)
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:89)
... 8 more
{code}
I used the following configuration:
{code:java}
name=CamelJiraSourceConnector
connector.class=org.apache.camel.kafkaconnector.jira.CamelJiraSourceConnector
tasks.max=1
key.converter=org.apache.kafka.connect.storage.StringConverter
value.converter=org.apache.kafka.connect.storage.StringConverter
camel.component.jira.jiraUrl=http://localhost:8080
camel.component.jira.password=xxx
camel.component.jira.username=user
camel.source.endpoint.jiraUrl=http://localhost:8080
camel.source.endpoint.username=user
camel.source.endpoint.password=xxx
camel.source.path.type=newComments
topics=mytopic
{code}
I also tried with OAuth, but run into the same issue. Furthermore I tested it
with Jira Online, but faced the same issue.
Using DEBUG/TRACE log did not really help me. I do not really understand the
underlying issue.
It is also not clear to me why there are configurations for components and
source.endpoints. What is the difference?
was (Author: stuber):
Hi guys
I am also struggling with the same issue. I followed the provided documentation
and took the configuration base from the projects example.
I always run into the following error:
{code:java}
[2020-07-07 00:12:11,684] ERROR WorkerSourceTask{id=CamelJiraSourceConnector-0}
Task threw an uncaught and unrecoverable exception
(org.apache.kafka.connect.runtime.WorkerTask:186)
org.apache.kafka.connect.errors.ConnectException: Failed to create and start
Camel context
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:103)
at
org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:213)
at
org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:184)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:234)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: Cannot find endpoint with scheme
jira
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.doAsEndpointUri(AbstractCamelCatalog.java:684)
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.asEndpointUri(AbstractCamelCatalog.java:673)
at
org.apache.camel.kafkaconnector.utils.TaskHelper.buildUrl(TaskHelper.java:44)
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:89)
... 8 more
{code}
I used the following configuration:
{code:java}
name=CamelJiraSourceConnector
connector.class=org.apache.camel.kafkaconnector.jira.CamelJiraSourceConnector
tasks.max=1
key.co
[jira] [Commented] (CAMEL-15269) How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
[
https://issues.apache.org/jira/browse/CAMEL-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152506#comment-17152506
]
Thomas commented on CAMEL-15269:
Hi guys
I am also struggling with the same issue. I followed the provided documentation
and took the configuration base from the projects example.
I always run into the following error:
{code:java}
[2020-07-07 00:12:11,684] ERROR WorkerSourceTask{id=CamelJiraSourceConnector-0}
Task threw an uncaught and unrecoverable exception
(org.apache.kafka.connect.runtime.WorkerTask:186)
org.apache.kafka.connect.errors.ConnectException: Failed to create and start
Camel context
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:103)
at
org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:213)
at
org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:184)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:234)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: Cannot find endpoint with scheme
jira
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.doAsEndpointUri(AbstractCamelCatalog.java:684)
at
org.apache.camel.catalog.impl.AbstractCamelCatalog.asEndpointUri(AbstractCamelCatalog.java:673)
at
org.apache.camel.kafkaconnector.utils.TaskHelper.buildUrl(TaskHelper.java:44)
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:89)
... 8 more
{code}
I used the following configuration:
{code:java}
name=CamelJiraSourceConnector
connector.class=org.apache.camel.kafkaconnector.jira.CamelJiraSourceConnector
tasks.max=1
key.converter=org.apache.kafka.connect.storage.StringConverter
value.converter=org.apache.kafka.connect.storage.StringConverter
camel.component.jira.jiraUrl=http://localhost:8080
camel.component.jira.password=xxx
camel.component.jira.username=user
camel.source.endpoint.jiraUrl=http://localhost:8080
camel.source.endpoint.username=user
camel.source.endpoint.password=xxx
camel.source.path.type=newComments
topics=mytopic
{code}
I also tried with OAuth, but run into the same issue. Furthermore I tested it
with Jira Online, but faced the same issue.
Using DEBUG/TRACE log did not really help me. I do not really understand the
underlying issue.
It is also not clear to me why there are configurations for components and
source.endpoints. What is the difference?
> How install CAMEL-JIRA-KAFKA-CONNECTOR in Jira
> --
>
> Key: CAMEL-15269
> URL: https://issues.apache.org/jira/browse/CAMEL-15269
> Project: Camel
> Issue Type: Task
> Components: camel-jira
>Reporter: Daniel Caloto Suárez
>Priority: Major
>
> Hello
> I'm new to kafka. I would like to know how to install the
> CAMEL-JIRA-KAFKA-CONNECTOR and how to configure it.
> Where do I have to put the unit
>
> org.apache.camel.kafkaconnector
> camel-jira-kafka-connector
> x.x.x
>
>
> Where to extract the file
> camel-jira-kafka-connector-0.3.0-package.tar.gz
> Where and how to set options such as
> camel.source.endpoint.jql
> Thank you very much for everything
> Dani
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152218#comment-17152218
]
Aashna Jena commented on CAMEL-14952:
-
As I mentioned during the call today, I had prepared a config file with
selectors similar to this one, but according to me, this poses maintenance
issues. Versions, menu items, and blog categories are not fixed. We keep
adding/changing categories, versions, and menu items, that's why I was against
the idea of having to specify them explicitly in the config file, especially
because it will mean that we have to put a PR on the Algolia repo every time we
make a change. We have recently also merged two pages - docs and projects, and
we might add/delete more webpages in the future, that's why I don't want to
keep explicit start_urls as well - although this we might require to some
extent.
My idea was to keep the config file that I've suggested on the PR + add one new
selector for Blog where lvl0 = "Blog", lvl1 = header a.category, and lvl2=h1
and add the categories page in stop_urls to stop duplicating results. This way,
we won't need an explicit set of categories. I'll wait for some more opinions
before I make changes, because [~Aemie] and I seem to be suggesting very
different things.
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152180#comment-17152180
]
Aemie commented on CAMEL-14952:
---
[~zregvart] [~delawen] [~aashnajena] I have updated the apache_demo.json. I am
aware that it's really long but when I went through the config of a heavily
distributed documentation based website, either the versions have different
configs or it's a huge config according to specifications. With the one I have
created, it will even notify the user that:
* Which search is under category and which one is under blog.
* Every menu item under the community will be visible alongside the community.
* For each doc, the names won't clash and no possible loopholes will be
created as I have tested
I understand we want to minify the file as much as possible but I strongly
believe we require the use of start_urls and the different specific selectors.
If [~aashnajena] can resolve those earlier stated points with a minified
version, then that's good ( I will think about it as well ), or else we could
work on this current and move on to minify it.
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aemie updated CAMEL-14952:
--
Attachment: (was: apache_demo.json)
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aemie updated CAMEL-14952:
--
Attachment: apache_demo.json
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151996#comment-17151996
]
ASF GitHub Bot commented on CAMEL-14952:
aashnajena commented on pull request #423:
URL: https://github.com/apache/camel-website/pull/423#issuecomment-654210877
About the first point, we can include the toolbar links without specifying
selectors, but I don't think it's a good idea to have all the links from the
toolbar. That would make the headings very long and repetitive for most
components. I'd wait for some more reviews on this part. We need to make a call
about how much of the hierarchy we want to show. My intent is to have one
high-level topic - which should be used for **grouping** results, and the rest
of the headings to consist of h1 and h2 only.
I agree that we need to treat blogs differently. I'll try to push some
changes for that soon!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151976#comment-17151976
]
ASF GitHub Bot commented on CAMEL-14952:
AemieJ edited a comment on pull request #423:
URL: https://github.com/apache/camel-website/pull/423#issuecomment-654193808
I have a few comments on these changes :
* You have only included the first child of the toolbar list and neglected
the rest. However, if you search for `Bean`, there is Bean under `Components`
as well as `EIP`. Hence, I suggested including the links of the toolbar to
avoid any cases of such behavior. If we were to use specific selectors, there
would be no loophole. If there is another possible workaround and it works,
that's good then.
* Another suggestion: Initially we made changes to the docs pages so that
the title wasn't the only thing shown in the search result. I believe we can do
the same with blog pages. The hierarchy I would prefer seeing the Blog as -
```
# This being for the blog pages
Blog
---
Category Name > Title of the blog
```
* Another case that is not taken care of is that when you search a
particular blog, it gives results from the
`https://camel.apache.org/category/` as well. To pass this case, I was
thinking that we can't avoid crawling on categories as it could be the page
where the user wants to land on however to avoid confusion on whether it is the
blog page or the category page, we could provide specific layout such as -
```
# This being for the category pages
Category Name
---
Title of the Blog
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151974#comment-17151974
]
ASF GitHub Bot commented on CAMEL-14952:
AemieJ commented on pull request #423:
URL: https://github.com/apache/camel-website/pull/423#issuecomment-654193808
I have a few comments on these changes :
* You have only included the first child of the toolbar list and neglecting
the rest. However, if you search for `Bean`, there is Bean under `Components`
as well as `EIP`. Hence, I suggested including the links of the toolbar to
avoid any cases of such behavior. If we were to use specific selectors, there
would be no loophole.
* Another suggestion: Initially we made changes to the docs pages so that
the title wasn't the only thing shown in the search result. I believe we can do
the same with blog pages. The hierarchy I would prefer seeing the Blog as -
```
# This being for the blog pages
Blog
---
Category Name > Title of the blog
```
* Another case that is not taken care of is that when you search a
particular blog, it gives results from the
`https://camel.apache.org/category/` as well. To pass this case, I was
thinking that we can't avoid crawling on categories as it could be the page
where the user wants to land on however to avoid confusion on whether it is the
blog page or the category page, we could provide specific layout such as -
```
# This being for the category pages
Category Name
---
Title of the Blog
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the searc
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151928#comment-17151928
]
ASF GitHub Bot commented on CAMEL-14952:
aashnajena commented on pull request #423:
URL: https://github.com/apache/camel-website/pull/423#issuecomment-654142579
@zregvart please trigger the preview now, PR is ready for review
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15248) Create ArangoDB camel component
[ https://issues.apache.org/jira/browse/CAMEL-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151911#comment-17151911 ] Zineb BENDHIBA commented on CAMEL-15248: (y) I'm working on it !! > Create ArangoDB camel component > --- > > Key: CAMEL-15248 > URL: https://issues.apache.org/jira/browse/CAMEL-15248 > Project: Camel > Issue Type: Improvement >Reporter: Omar Al-Safi >Priority: Minor > Fix For: 3.x > > > [ArangoDB|https://www.arangodb.com/] is a graph database that is gaining a > good momentum in the area of graph database, and thus would be valuable to > have a component for it in Camel. > [ArangoDB Java Driver|https://github.com/arangodb/arangodb-java-driver] has > Apache 2.0 license and hence shouldn't be an issue to include the driver in > the dependencies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151901#comment-17151901
]
ASF GitHub Bot commented on CAMEL-14952:
aashnajena commented on a change in pull request #423:
URL: https://github.com/apache/camel-website/pull/423#discussion_r450090271
##
File path: antora-ui-camel/src/js/vendor/algoliasearch.bundle.js
##
@@ -4,8 +4,8 @@
const algoliasearch = require('algoliasearch/lite')
window.addEventListener('load', () => {
-const client = algoliasearch('BH4D9OD16A',
'16e3a9155a136e4962dc4c206f8278bd')
-const index = client.initIndex('apache_camel')
+const client = algoliasearch('QDOJ4LJQCC',
'0fa28c3acc4d5f383b85ae4ad035ac9c')
+const index = client.initIndex('aashna')
Review comment:
As I mentioned, I've linked my personal index here, which is named
"aashna". This is just for showing everyone how the search results will look
with the new configuration. These two lines are not supposed to be merged, I
will revert them before merging.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151898#comment-17151898
]
ASF GitHub Bot commented on CAMEL-14952:
AemieJ commented on a change in pull request #423:
URL: https://github.com/apache/camel-website/pull/423#discussion_r450085459
##
File path: antora-ui-camel/src/js/vendor/algoliasearch.bundle.js
##
@@ -4,8 +4,8 @@
const algoliasearch = require('algoliasearch/lite')
window.addEventListener('load', () => {
-const client = algoliasearch('BH4D9OD16A',
'16e3a9155a136e4962dc4c206f8278bd')
-const index = client.initIndex('apache_camel')
+const client = algoliasearch('QDOJ4LJQCC',
'0fa28c3acc4d5f383b85ae4ad035ac9c')
+const index = client.initIndex('aashna')
Review comment:
The name should be `apache_camel`, I believe.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151862#comment-17151862
]
ASF GitHub Bot commented on CAMEL-14952:
aashnajena opened a new pull request #423:
URL: https://github.com/apache/camel-website/pull/423
I have linked my own Algolia index to this PR for now, so that everyone can
view the changes in search results.
- Search results are now grouped by higher level headings eg. "Camel
Components" or "User Manual" or "Camel Kafka Connector".
- For Hugo pages, search results are grouped by H1, because that itself is
the highest level of heading eg "Articles" or "Books"
- I wanted to make the config file as simple as possible, and depend on the
sitemap instead of the URLs. This is what I'm using :
"sitemap_urls": [
"https://camel.apache.org/sitemap.xml";
],
"selectors": {
"lvl0": ".toolbar ul li:nth-child(1) a",
"lvl1": ".version-menu a.is-current",
"lvl2": "article h1",
"lvl3": "article h2",
"text": "article p, article li"
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Attachments:
> BH4D9OD16A_apache_camel_20200608-20200614_no_result_searches.csv,
> List_Of_Crawled_Pages_by_DocSearch.txt, apache_demo.json, camel.json,
> getbootstrap-searchresult.png, image-2020-06-13-14-39-08-776.png,
> list_of_crawled_pages.txt, sitemap-camel.png
>
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151853#comment-17151853 ] Ganesh commented on CAMEL-11780: Hi, This PR doesn't seems to be merged to the master. If the SSL support is already done in the camel-amqp component in another way (refactored), then please explain in this ticket and close this ticket. Thanks a lot. > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Priority: Major > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
