I've been looking for this for a while and haven't found anything yet. Is there any reason to that ? I would like to proxy a solr server with the camel integration framework and I understand it must be quite straight forward without it, but less elegant :).
If someone has worked on this, I would love some feedback.
Nicolas.
yep, there is a new camel-solr component
There is an Apache Lucene component
http://camel.apache.org/lucene
But I dont think anyone has done any Apache Solr component. However in the end its all Java code, so you should be able to leverage them together.
Also check out github as people spin off projects there creating all kind of Camel related components.
There is a camel-solr component proposal https://issues.apache.org/jira/browse/CAMEL-4539
I have build a Camel Solr endpoint as part of a search project. Solr and Camel fits smoothly and I have had no problems. Its available at here. Its still in the early days, i.e. I'm writing the documentation and testing as we speak.
It would be great if you could try it out and provide feedback, both to its usage as well as to the documentation.
Cheers
Related
I searched in web but did not find any explanation that what is the exactly CamelContext? where and how to use ?
I gone through below links also but not satisfied with explanation.
https://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html
https://dzone.com/articles/apache-camel-tutorial-eip
There are many comparision for CamelContext with others, but what I am looking for is the what is it? I want some conceptual explanation.
Please help me to understand this.
It's roughly an instance of a Camel environment, or at least it's a reference to it. Most apps would only have one CamelContext, but you can have several if needed. Looking at the referenced document, it shows how the context has a lifecycle.
In most cases, the context will start and stop along with the application.
After seeing the videos in YouTube, I knew about the Apache camel framework,
and from that I got the answer that camelcontext is nothing but context of the 'apache camel framework' framework.
As many framework have context like Spring have an applicationcontext, Ninja have a context, same the 'Apache camel framework' have a context and that is called 'camelcontext'.
So, it is the run-time system of Apache Camel (framework) and it connects its different concepts such as routes, components or endpoints.
Reference :
Basic Apache Camel Tutorial
I am currently learning Camel, and have a specific project in mind that requires a Websphere MQ back-end, but I can't use JMS components, since I need a lot of non-jms headers, like MQIIH.
I found the camel-wmq project.
Is it the recommended solution ? Is it any good ?
You don't need to use jms. WMQ has a client API. Just download the wmq client jars and put them in your project and use them together with your Camel routes. You will probably put the wmq client code in a processor class or something similar. Off course best to test to put a message on a queue manually via RFHUTIL or something similar as a client so you are sure the environment setup is correct.
The suggested way of working with WMQ has always been through the JMS component since it enables you to painlessly switch to other providers if the need arises.
However, if you need to use some WMQ-specific function then my suggestion would be to extend the camel-wmq library - it contains only a subset of features supported by WMQ and does not support MQIIH headers that you need. Adding functionality to a component would probably involve more work than the solution Souciance Eqdam Rashti suggested but it would be a cleaner solution and more in line with Camel's philosophy. Also, you'd be giving back to the community and thus help make Camel a better tool for everyone :)
I would also suggest you go through the IBM MQ discussions on the Camel's official user group mailing list and see if you can salvage anything.
This two-year-old BitBucket “push-to-deploy” (https://cloudplatform.googleblog.com/2014/09/using-bitbucket-for-push-to-deploy.html) option looks really useful/interesting but seems like it’s no longer functional. The link in step 8 seems to have disappeared.
Is it possible to use this general feature somehow even if it doesn’t seem to work with BitBucket anymore?
If anyone has any ideas, it would be much appreciated. Thank you.
We use Jenkins for continuous integration and continuous deployment. You could take a look on https://jenkins.io/ .
I saw there was a article in the Apache wiki on OpenNLP for Solr.
Is it valid for current solr version 5.3.1?
No, if you have a look at LUCENE-2899, you'll see that the code discussed was never added to trunk. You'll have to download/patch/update the code yourself if you're going to have it native to Solr.
It's probably a better idea to do all the NLP stuff outside of Solr, then index the result in a form suited for the task you're trying to solve.
Yes. It's better to keep it outside.
Here is a small project I tried.
https://github.com/john77eipe/DeepQA
I'm really interested in being able to annotate my data. I am not really sure where to start, so I thought of using Apache Uima with Solr. I'm not sure if I'm no the right path, yet. Anyhow, I'm looking for some good documentation on this component called Solr-Uima
http://code.google.com/p/solr-uima/
Thanks,
J
I have no idea what UIMA is, but when I can't find any docs I read the tests. If the tests are not enough I read the code itself. (sorry if this is a generic answer, but this code doesn't seem to be too difficult to follow, so I really think it's a viable option).
The former project on Google Code has been contributed to Lucene / Solr codebase.
There is a wiki page, but needs to be updated.