I have used solr to index and search pdf files.. it is working fine. Now I am said to use Mahout to my project and was told to integrate it with solr. I am new to this technology so please do help me from scratch. in a basic way....
Do i need to download and inmstall mahout first or will modifications in schema and solrconfig will make it? for integrating tika functionality it was just modification in the config file.
Mahout is a separate project, so you have to download, install, and learn how to use it...will not be a one afternoon thing.
But, you should be aware of this Lucene clasiffication module (Solr is built on top of Lucene). It is not as complete as Mahout, but for not massive projects, with can work really well. The advantage is that it integrates with Lucene/Solr, so you have much less work to do. I have used successfully with Sorl4.6
Related
I am really a beginner in ELK stack. I want to learn a plugin building for Kibana. I see their documentation for plugin building (https://www.elastic.co/guide/en/kibana/current/development-plugin-resources.html)
But the thing is, it's not enough for me or I can't understand it properly. I want to customize the Kibana dashboard with some other functionalities I want. I want to build the plugin by ReactJs in front-end. If anybody has any resource or any example codes to share it would be a great help for me. I am using Kibana and ElasticSearch both version 7.4.2
This might be an old question, but since I am facing the same issue, so maybe someone else could use this answer.
I found this presentation by Elastic for how to build you own Kibana plugin, it is an old one, they are working on Kibana 5 I guess, but could be a good starting point for someone.
https://www.elastic.co/elasticon/conf/2016/sf/how-to-build-your-own-kibana-plugins
I have also found this article that is more recent and the author uses ELK 7
https://chunkbytes.com/how-to-create-a-plugin-for-kibana/
Im working with Jenkins DSL and pipelines. Where can I find DSL documentations for these plugins I've typically used GUIs to configure?
I find it hard to imagine that when a new plugin is published that it already supports DSL. (Or are they written in DSL?). Is there a way to find this documentation? Is there an example of a walkthrough to enumerate this?
Or is DSL support limited to 'first class citizen' plugins.
Some of the plugins I am using are azure, packer, maven. It's not the DSL documentation I am asking about, but going about hunting for it.
There isn't really a centralized place (that I know of) for this, as each plugin will publish its documentation differently.
In terms of where you can search:
Some plugin steps can be found on the jenkins.io website.
http://your-jenkins/pipeline-syntax for generated syntax for your version of Jenkins and plugin versions
The source code, since most Jenkins plugins are open source
I have faced a problem in our development project today. I wanted to create webservice in TomEE 1.6.0+ environment in the same way as I did earlier in Glassfish environment. I had a lot of trouble with it so I thought I try to replace Apache CXF with Sun Metro stack (version 2.3).
I haven't found any tutorial on it so I tried to do something myself. My solution was to delete all of the cxf-*.jar and openejb-cxf-*.jar from the TomEE lib folder and I have added webservices-*.jar (only the following 4 libraries: rt, tools, extra, extra-api) from the metro distribution. I have looked into the installation ant script and I have selected files based on the installation definition.
It looks now everything is perfect. Now I can work the same way with webservices as I worked before. My project deploys smoothly into TomeEE environment.
My question is quite simple now:
Is it a correct solution or looks like a hack?
Thanks in advance for any feedback.
The definitive answer would come from someone on the TomEE project, but I'm surprised this worked... but I'm happy it did for you.
TomEE has bindings to CXF for CDI for specific purposes: it can scan for jax-rs annotations, inject fields, expose services, etc (too many to enumerate). As long as your application isn't reliant on any of that functionality, you might be ok.
Since you're running an unsupported configuration, the key here is thorough testing. I would create a battery of integration tests (SOAP-UI?) that will get you a comfortable level of branch coverage... definitely at least cover your happy paths.
The nice thing about TomEE is that it's incredibly modular as you discovered. Good luck, and post back for the community how everything is going later on.
I am working on java web project based on solr search engine.
I am looking for an alternative pagination way because solr has a known bug using start and rows attributes.
Do you know a solution (solr or java)?
Consider I have a lot of contents from query.
Thanks in advance
Looking for the maven archetype/template for google app engine Objectify + google web toolkit Platform. ( We don't need any Spring code. )
We need a version that can work immediately to build, compile, debug locally and to upload to app engine.
It needs to be able to generate eclipse (Indigo) project file and to be imported to eclipse trouble-free.
This is a late answer but a good one I think :
https://github.com/ArcBees/ArcBees-tools/tree/master/archetypes/gwtp-appengine-objectify
You can have a look at http://code.google.com/p/gwtgae2011/source/browse/pom.xml. Not sure if it will work but I started using that one and then fixed the issues I had. It's not perfect but I can develop in Eclipse with my fixed pom file.
You can use this http://www.kindleit.net/maven_gae_plugin/examples/index.html as a reference. It has Objectify and GWT specific examples (separate types though).
I know the Objectify version works, though it will require a bit of tweaking to meet your specific needs. The gae.version used was kind of old, but no problem switching it 1.6.0.