|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 12
Messages: 12
Messages: 12
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Compass 1.2, providing search capabilities for object models, released
Compass, a Java Search Engine Framework, has released version 1.2. Compass simplifies the integration of search functionality into any Java application. It is built on top of the excellent Lucene library and adds several features on top of it (most notably, transactional support, including long running transactions).
Compass allows to map your domain model (Object, pure XML, and the map like Compass Resource) into the search engine simply using either xml or annotations, and integrates with leading ORM libraries (Hibernate, TopLink, OpenJPA) and web frameworks (Spring MVC, Grails) in order to simplify even more the introduction of search into an application. A nice write-up on why Compass or Search make sense can be found here and the birth of Compass is still valid on how it came to be.
Does search functionality is a must have in an application? Do you agree that search feature can be much more than just a "google like" search box in your website and actually change the way people interact with applications (ala Google Desktop or Mac Quicksilver)?
|
|
|
Message #241276
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
So how does this stack up to Hibernate Search ?
|
|
|
Message #241277
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
maven repository release
A release into the maven repository would be nice and lower the barrier, against atleast me trying it, a bit.
|
|
|
Message #241308
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Compass 1.2, providing search capabilities for object models
What abt Mapping and configuration xml files of compass 1.0? :) Is it easy now?
|
|
|
Message #241333
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Hibernate Search is an unbelievably complicated architecture for clustered J2EE applications. I dont know what is the idea of having shared/locked directory and JMS, when all you need is jdbc datastore for lucene with write-behind which can take care of transaction, backup, clustering etc.
It looks like compass has jdbc store. but it does not clarify if that solves the clustering problem. anybody knows?
|
|
|
Message #241346
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Compass is amazing
Hi,
Congrats to the Compass team !
"Full text", Google-like search on Objects is really amazing. I'm a huge fan of the approach in general, and definitly agree with the foundations you describe in the referenced blog post (which I had not read before). A small "search" input field is definitly easier and more comprehensive than bloated forms with dozens of widgets... Even for "advanced searches", the Compass syntax makes retrieving objects simple, and accurate.
On the technical side, so far Compass has met ALL of my expectations, and even more. Integrating it with other popular technologies like Hibernate and Spring is a no brainer, and so is the mapping using annotations : enabling search on Domain POJOs is a matter of minutes ! Then, for more advanced use cases, the analyzers and query API allows fantastic stuff I would not even have dreamt of with xxxQL...
To me, this "feature" is one of the most interesting stuff in OOP land currently. It opens really cool perspectives for building better applications.
Thanks to the team, and keep up the good work !
Cheers
Remi
PS : agreed with the other poster for the maven repo release... This would definitly be nice !
|
|
|
Message #241394
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
It looks like compass has jdbc store. but it does not clarify if that solves the clustering problem. anybody knows?
I'm also interested in this. Also, do you know if there are any other commonly available (hopefully standalone) JDBC store / 'Directory' implementations for lucene? It should not be rocket science to make one.
I'v clustered Lucene using it's RAMDirectory with Terracotta, but would like to give a JDBC based aproach a try.
/Henri Karapuu
|
|
|
Message #241403
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Lucene Jdbc Directory: An implementation of Lucene Directory to store the index within a database (using Jdbc). It is separated from Compass code base and can be used with pure Lucene applications.
Looks like this itself is standalone.
|
|
|
Message #241412
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Hibernate Search is an unbelievably complicated architecture for clustered J2EE applications. I dont know what is the idea of having shared/locked directory and JMS, when all you need is jdbc datastore for lucene with write-behind which can take care of transaction, backup, clustering etc.
It looks like compass has jdbc store. but it does not clarify if that solves the clustering problem. anybody knows?
When you have your "jdbc datastore for lucene with write-behind which can take care of transaction, backup, clustering" that scales out as much as the proposed clustering architecture for Hibernate Search, let me know :)
And if, you make it work, then just write a one class DirectoryProvider for Hibernate Search to wrap that up. Just like Compass, Hibernate Search are not tied to one architecture whether clustered or not.
Back to the main topic, congrats to Shay :)
|
|
|
Message #241416
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Emmanuel,
1)If the indexes are stored as tuples (unlike file system which gets locked completely) i do not see any reason why it can't scale.
2)If you are justifying JMS architecture for scaling for search indexing (which could be less than 10% of persistence need in an app), why are we not doing that for all persistence needs (including hibernate)?
3)For all this complexity, basic transactional integrity is not guaranteed. While hibernate search talks about transaction, if the transaction fails, integrity goes for a toss (with lucence lock exception) and indexing for subsequent users/threads fail.
4)By reading the document i felt shared dir & JMS were the only 2 architectures possible for clustering, which i understand now is not true. If so, pls update the document.
BTW, I made the comment for comparison and not to pull down hibernate search. And the fact remains that Compass came with lucene jdbc implementation which could enable a much simpler and better architecture.
mani
|
|
|
Message #241418
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Emmanuel,
1)If the indexes are stored as tuples (unlike file system which gets locked completely) i do not see any reason why it can't scale.
2)If you are justifying JMS architecture for scaling for search indexing (which could be less than 10% of persistence need in an app), why are we not doing that for all persistence needs (including hibernate)?
3)For all this complexity, basic transactional integrity is not guaranteed. While hibernate search talks about transaction, if the transaction fails, integrity goes for a toss (with lucence lock exception) and indexing for subsequent users/threads fail.
4)By reading the document i felt shared dir & JMS were the only 2 architectures possible for clustering, which i understand now is not true. If so, pls update the document.
BTW, I made the comment for comparison and not to pull down hibernate search. And the fact remains that Compass came with lucene jdbc implementation which could enable a much simpler and better architecture.
mani
Maybe performance (speed) figures for a filesystem based vs. jdbc based Lucene Directory are different.
Jdbc-based solution promote the "embedding" of fulltext engine in the using app and increased load on your DBMS since, I think, Lucene Directory tables should be in the same
DB of your data, otherwise you should go into true 2PC.
When the above become issues, the solution is to think at the
full-text service as an independent service with its own balancing architecture.
The web app would use any high performance IPC (ICE, primarily, or IIOP) for RPC.
Obviously, a wise use of interfaces would allow for total transparency of the underlying implementation.
Guido
|
|
|
Message #241434
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Compass 1.2, providing search capabilities for object models
Emmanuel,
1)If the indexes are stored as tuples (unlike file system which gets locked completely) i do not see any reason why it can't scale.
2)If you are justifying JMS architecture for scaling for search indexing (which could be less than 10% of persistence need in an app), why are we not doing that for all persistence needs (including hibernate)?
3)For all this complexity, basic transactional integrity is not guaranteed. While hibernate search talks about transaction, if the transaction fails, integrity goes for a toss (with lucence lock exception) and indexing for subsequent users/threads fail.
4)By reading the document i felt shared dir & JMS were the only 2 architectures possible for clustering, which i understand now is not true. If so, pls update the document.
BTW, I made the comment for comparison and not to pull down hibernate search. And the fact remains that Compass came with lucene jdbc implementation which could enable a much simpler and better architecture.
mani
Mani, I have my reasons for going the way Hibernate Search has been designed and to partly disagree with your statements. I don't think this forum post is the appropriate medium to talk about it, but feel free to start a thread in the Hibernate Search forum and I will be more than happy to have this discussion with you, it should be interesting and I think I will convince you :). And as I said, if the JDBCDirectory is what you want, you just need to write a one class provider to Hibernate Search: Sylvain has done that reusing the Compass JDBCDirecotry implementation.
|
|
|
Message #241479
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: maven repository release
+1
Nice project but it would be good to be able to get something up and running quickly with maven.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman continues to explore the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(January 21, Article)
Ted Neward is an independent consultant specializing in high-scale enterprise systems, and an authority in Java and .NET technologies. He is the author and co-author of several books, including Effective Enterprise Java. At TheServerSide Java Symposium in March, he will be presenting sessions on pragmatic architecture, ECMAScript and Scala.
(January 15, Article)
Now that Oracle is absorbing Sun Microsystems, there mixed views on what should come of the Java Community Process (JCP). While some say Oracle should become the new steward of Java and keep the JCP much as it was, others argue that it may be time to open-source this widespread language.
(November 24, Article)
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
