InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

InfoQ Article: Compass Introduction, Compass 1.1 M3 now available

Posted by Rob Thornton on Nov 30, 2006

Sections
Development,
Architecture & Design
Topics
Java ,
Search
Tags
Compass

InfoQ has released a new article describing how to use Compass, an open source Java Search Engine Framework. The article introduces Compass and walks through some examples of using the API, the RSEM, OSEM, and XSEM mappings and briefly describes Compass Gps, a module that allows you to integrate Compass with ORM tools, among other data sources.

The Compass team recently released version 1.1 M3. One of the new features is support for polymorphic relations when using OSEM. Shay Banon, project lead, lists the major features in this release as:

  • Support for polymorphic relationships: Compass now supports polymorphic relationships when using OSEM. Poly relationships are automatically identified by Compass, and all the relevant mappings are detected and added. In case of one to one mappings or one to many using generics, the mappings are detected based on the class name. One to many relationship without generics can use a single reference alias mapping, with the rest of the derived mappings automatically used. There is still an option to explicitly list all the aliases using comma delimited list in the ref-alias.
  • Better cyclic mappings support: Compass now handles cyclic relationships much better, especially for component mappings. Note, since most times cyclic relationships are simply same objects referencing each other, max-depth value changed to 1 (from 5). In case of tree based cyclic relationship, max depth should probably be set to a higher value.
  • FS Transactional Log: Read committed transactions can now store most of the transaction log on the file system. This allows for bigger transactions to be executed under read committed on expense of performance. Current memory based transaction log is also supported (and is the default).
  • Runtime Settings: Certain settings can now be set on the session level, changing part of Compass behavior on a per session resolution. First runtime settings supported are the transaction log used for the current session.
  • JdbcDirectory support Oracle 9: Jdbc directory and storing the index in the database now support Oracle 9i.
  • Initial XA Support: Compass can now join an XA transaction by enlisting itself as an XA resource within a JTA transaction manager including participation in two phase commit. Resume crashed transactions is not supported.
  • Performance Improvements

See the full release notes for more information. InfoQ covered the M2 release back in September.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.