summa-announce — Announcements regarding Summa - low traffic

[Summa-announce] This mailing list will be closed

[Toke E. <te...@st...>]

Summa was moved to SourceForge at http://sourceforge.net/projects/summa/
2-3 years ago. It has recently been decided at Statsbiblioteket that
Summa will no longer be actively supported as an Open Source project.

Summa is still kept and maintained actively on SourceForge, but support
in the form of bugfixes and feature requests has low priority if the
issues does not affect the production installation at Statsbiblioteket.

As a consequence of the move, this mailing list will be shut down within
the next few days. Readers are welcome to contact me directly.

Regards,
Toke Eskildsen (te...@st...)
Lead developer on the Summa project, Statsbiblioteket

[Summa-announce] Summa 1.6.7

[Henrik K. <hb...@st...>]

Hallo out there,

We have a new version of Summa, 1.6.7. 

The release not can be found here:

========================
2010-11-24: Summa 1.6.7
========================

 * Bugfix: Reversed heritrix to 1.14.3 due to conflict with apache 
   commons lang 2.1.

 * Bugfix: Removed faulty doctype for service.xml for non java 
   properties files.

 * Feature: The base statistic table is used and updated. This is a
   fixe for #110.
   Implemented use of base statistic table, when ever status/holdings 
   are called and invalidating it when ingest is done.

 * Fixed bug #87, it is now possible to delete suggestion from the
   suggestion storage, either via the suggest-tool or the web
   service.

The download can be found here

http://sourceforge.net/projects/summa/


Best regards

-- 
Henrik Bitsch Kirk, Java developer, +45 8946 2376
Statsbiblioteket, Victor Albecks Vej 1, 8000 Århus C
CVR/SE 10100682 - EAN 5798000791084
www.statsbiblioteket.dk<http://www.statsbiblioteket.dk>

[Summa-announce] Summa release 1.6.6

[Henrik K. <hb...@st...>]

Dear Summa's

This release is a hotfix, to users, have existing storage where it had failed to ingest with 1.6.5.

The newest version of summix can be found here
sourceforge.net/projects/summa/


Best regards
-- 
Henrik Bitsch Kirk, Java developer, +45 8946 2376
Statsbiblioteket, Victor Albecks Vej 1, 8000 Århus C
CVR/SE 10100682 - EAN 5798000791084
www.statsbiblioteket.dk<http://www.statsbiblioteket.dk>

[Summa-announce] Summa 1.6.5 release

[Henrik K. <hb...@st...>]

Girls and boys the new Summa 1.6.5 has just been released.

The news file contains the following key points.

========================
2010-11-03: Summa 1.6.5
========================

 * Bugfix: StorageWS re-initialized for each session, putting
   garbage in perm space, making a lot of external request and
   generally performed horribly.

 * Bugfix: fixed last modification time for all base, which was
   wrongly set when a databsase storage was closed an restarted.
   This is a fix for #109

 * Feature: The FileReader now sets lastModificationTime for files
   marked as completed

This release can be downloaded from sourceforge
http://sourceforge.net/projects/summa/files/releases/1.6.5/summix-1.6.5.zip/download

-- 
Henrik Bitsch Kirk

[Summa-announce] ANNOUNCE: Summa 1.6.2 release

[Henrik K. <hb...@st...>]

Summa is now released in version 1.6.2. This release brings along some bugfixes.

As usual the files are on:
 
https://sourceforge.net/projects/summa/files/releases/1.6.2

========================
2010-07-26: Summa 1.6.2
========================

 * Major lookover of the Shell components. The following features are 
   added:
	 - 'clear' command to core shell - it obviously is clearing the shell.
	 - Added support for aliases in core shell functionality.
	 - Tab-completion for core shell for known commands and aliases.

 * Change: Record was changed to accept null as content by assigning 
   a byte-array of length 0 when null was received. This was done to
   support pseudo-records consisting only og id and base.

 * Bugfix: Fixed bug where missing records from a fulldump where not
   deleted, this was due to a mistake in the ResultSetCursor, where
   newly created records wasn't returned.
	  
 * Bugfix: Handling XML CDATA blocks correct. Tracker ID #96.

 * Bugfix: Removed possible NullPointerException in ShellContextFeedback.

Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.6.1 release

[Henrik K. <hb...@st...>]

Summa is now released in version 1.6.1. This release brings along some bugfixes.

As usual the files are on:
 
https://sourceforge.net/projects/summa/files/releases/1.6.1

The release summary reads:

========================
2010-06-22: Summa 1.6.1
========================

 * The DocIDCollector did not tahe docBase into account when
   collecting IDs for faceting.

 * Feature: Added XSLT to convert from SummaDocument to SolrDocument.

Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.6.0 release

[Henrik K. <hb...@st...>]

Summa is now released in version 1.6.0. This release brings an long awaited upgrade to Lucene 3.0.1.

As usual the files are on:
 
https://sourceforge.net/projects/summa/files/releases/1.6.0

The release summary reads:

========================
2010-06-07: Summa 1.6.0
========================

 * Upgrade Lucene to version 3.0.1.

 * Feature: Added lowercase analyzer, see SummaLowercaseAnalyzer

 * Moved progress.xml to root of persistent directory.

 * Known bug: Supplied data to Summix isn't working.

Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.5.5 release

[Henrik K. <hb...@st...>]

Summa is now released in version 1.554. This release brings besides small bug fixes, also some new filters, upgrade to H2 1.2.32, among other things. See the NEWS ad Changelog files for all changes.
NOTE: This is the last Summa release before changing to Lucene 3.0.1.

As usual the files are on:
 
https://sourceforge.net/projects/summa/files/releases/1.5.5

The release summary reads:

========================
2010-05-25: Summa 1.5.5
========================

 * Feature: It is now possible to query getModifiedRecords for just
   id, base etc. and get these faster. 

 * Feature: added support for getting multipled records in one go.

 * Feature: Support for granularity and ignore-changes-newer-than
   for rss feed on status page.


Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.5.4 release

[Henrik K. <hb...@st...>]

Summa is now released in version 1.5.4. This release brings besides small bug fixes, also the first stable Did-You-Mean service. 
Both the status and sample website show the running version number.
Lastly this release brings a cleanup of ant scripts.

As usual the files are on:
 
https://sourceforge.net/projects/summa/files/releases/1.5.4

The release summary reads:

========================
2010-03-24: Summa 1.5.4
========================
 
 * Feature: Did-You-Mean service built index on start-up, iff index 
   is not already present. Searching while building index results in 
   an empty search response.
   Added DidYouMean support to the sample website.
 * Feature: Status and Sample website now shows version number and
   revision tag. This fixes #78 in tracker.



Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.5.3 release

[Henrik K. <hb...@st...>]

Summa has just reached 1.5.3. This release brings a new filter which from a full dump do an update, a new ant target which generate unit test report and support for RAM as well as FS directory when using the Did-You-Mean service.
Notice the Did-You-Mean service is still under development.

As usual the files are on:

https://sourceforge.net/projects/summa/files/releases/1.5.3

The release summary reads:

========================
2010-03-11: Summa 1.5.3
========================

 * NOTICE: The didYouMean web services is only experimetal. API and 
    configuration keys may still change.
 * Added UpdateFromFulldumpFilter which from a fulldump treat the dump
 	  as an update on a single base.
 * Feature: Added Did-You-Mean support for FSDirectory as well as
	  RAMDirectory. This is a configuration.
 * Feature: Added junit test functionality to all ant files, which
	  include generating xml and html files for showing result of junit
	  tests on a single webpage.
	  NOTE: The control module, is not working at this point.


Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.5.2 release

[Henrik K. <hb...@st...>]

Summa has reached 1.5.2 which have just been released. This among other features a new highly experimental web service, did-you-mean. Other that that som bugfixes and added documentation.

As usual the files are on:

https://sourceforge.net/projects/summa/files/releases/1.5.1

The release summary reads:

======================== 
2010-02-19: Summa 1.5.2 
========================    
 * NOTICE: The didYouMean web services is only experimetal. API and
  configuration keys may still change.  
 * Feature: Expose a didYouMean webservice under the standard
  SearchWS.
 * Feature: Implement a 'batchjob' command for storage-tool.sh
 * Release includes all xsd schemas for xml responses found in
  /doc/schema/ 


Best regards,
Henrik

[Summa-announce] ANNOUNCE: Summa 1.5.1

[Mikkel K. E. <mk...@st...>]

Hot in the heals of 1.5.0 we bring you a small bug fix release. The only
change in this release is a minor bug in the status service.

As usual the files are on:

  https://sourceforge.net/projects/summa/files/releases/1.5.1

The release summary reads:

========================
2010-02-05: Summa 1.5.1
========================

 * Bugfix: Proper escaping of messages from sub-services in the status web
           service. The status web service would return invalid XML if any
           of the monitored services returned properties with names that
           was not valid XML

Cheers,
Mikkel

[Summa-announce] ANNOUNCE: Summa 1.5.0 and license change to Apache 2

[Mikkel K. E. <mk...@st...>]

On behalf of the Summa team I am proud to announce the immediate
availability of Summa 1.5.0. It's been almost two months since our last
release, which means that this has been a longer release cycle than
usual. Indeed this announcement mail is also longer than usual so go
grab a cup'a before you read on.

As always you can get the release from:

https://sourceforge.net/projects/summa/files/releases/1.5.0

ABI BREAK
First of all you might have noticed that the minor version has been
bumped from 4 to 5. This is because we had to break the binary interface
(ABI) in order to roll in some new features. API and source
compatibility has been retained, so fear not.

What an ABI break means that RMI services can not talk together because
the wire format of the serialized classes have changed. This means that
you have to upgrade you entire Summa stack to the 1.5.0 series in one go
if you want to make the change.

NOTABLE NEW FEATURES
The reason that we changed the ABI was in order to add some new methods
to the Storage interface. The biggest visible change is the new
Storage.batchJob() method. It allows you to run a script that resides in
the classpath of the Storage process on a specified subset of the
storage. The script can be in any scripting language supported by the
JVM via the ScriptEngine SPI. This has been tested with the native
Javascript support of Java 6 as well as Python/Jython (requires Jython
>= 2.5.1 in the classpath).

We have also added variants of Storage.flush() and Storage.flushAll()
that takes a set of metaflags affecting how the flushed record(s) should
be updated. One new thing enabled this way is the flag that says not to
update a record if it is already stored in the same state (eg. all
fields are identical).

LICENSE CHANGE
We have changed the license to Apache 2 (was LGPL 2 before that). There
are many reasons for this, but a few of the main ones are:

 - Ease code flow between Summa and Lucene, and Summa and Solr. This is
   especially important now that we are engaging more in upstream
   development (more on this in the blog later[1]).

 - Ease vendor adoption. It is a known fact that some vendors stay away
   from copyleft licenses by principle. Whether or not this is a good
   thing is besides the point, we just want people to deploy Summa
   anywhere it's applicable

RELEASE SUMMARY
The release summary is longer than usual and includes, not only new
features, but also some important bug fixes:

========================
2010-01-27: Summa 1.5.00
========================
	  
 * NOTICE: Convert entire Summa source tree to Apache 2 license

 * Storage ABI break (source compatibility preserved): Add variants
	  of flush() and flushAll() that takes an extra QueryOptions
	  parameter.

 * ABI break: Add setter methods for QueryOptions.meta(). We alreay
	  broke the Storage binary protocol so it's no biggie.

 * Update H2 dep. to 1.2.126, which among other fixes includes: "The
	  database is now closed after an out of memory exception, because
	  the database could get corrupt otherwise.". and disable the H2 
	  level 2 cache by default

 * New API Storage.batchJob for running predefined batch jobs in any 
 	  scripting language accrose of subsets of the storage.
	  Bundled sample batch jobs with Summix: 
	  collect_ids.job.js, delete.job.js, and count.job.js 
 
 * Add a 'holdings' command to storage-tool

 * Add a __holdings__ record to storage containing detailed storage 
 	  statistic. Show storage __holdings__ in status page and feed
	  The holdings can also be looked up with the "holdings" action in
	  storage-tool.sh

 * Define a meta flag "TRY_UPDATE", which alter default behaviour of 
	  Storage.flush() and Storage.flushAll() to not update records if they 
	  already are up to date.
	
 * New boolean property on RecordWriter:
	  "summa.storage.recordwriter.tryupdate" to pass TRY_UPDATE=true in
	  the QueryOptions to flushAll()

 * Bugfix: Allow both old and new H2 file formats in H2Storage and
	  SuggestStorageH2 (ie. allow both .data.db and .h2.db)

 * Bugfix: There was an elusive deadlock in QueuedInputStream used
	  by the ZipParser class. It both involved a missing 'synchronized'
	  statement and a bad cast of byte to int. We have replaced the
	  entire implementation with Java's native Piped{In,Out}putStream.

 * Bugfix: The result of an IndexLookup was scrabled when a
	  sortLocale was defined for the facet

 * Bugfix: The FacetResults did not perform entity escaping
	  correctly

 * Bugfix: UniqueTimestampGenerator.MAX_TIME was not constructed
	  correctly and was in fact negative!

 * Bugfix: LuceneManipulator kept running in the event of out of
	  disk space

 * BugFix: Tag-representations were double entity-encoded

 * Bugfix: The SortedPoolImpl was not thread-safe for reads

 * BugFix: Sort failed with an ArrayIndexOutOfBoundsException if
	  certain documents did not contain a term for the sort field

 * Bugfix: The sample website did not support sorted search or
	  paging

 * Bugfix: The MultipassSortcomparator works now, but used the
	  memory-inefficient BitsArrayInts
	  Testing: A bug has been discovered in BitsArrayPacked, where
	  assigning to a value nullifies the subsequent value

 * Feature: Made the LuceneManipulator optionally multi threaded
	  (deafult is 1 thread, which mimicks the old behaviour). As par of
	  this, the IndexManipulator-interface was extended with support
	  for signalling if the order of documents gets unreliable

 * Feature: Added filter for post-processing in ingest workflows
	  involving full dumps. The primary usage is clearing of old data
	  from Storage

 * Feature: Provided an option for enabling lenient marc-parsing in
	  ISO2709ToMARCXMLFilter

 * Feature: Made it possible to specify the sort comparators used by
	  a LuceneSearchNode, making it possible to choose between memory
	  usage and speed when sorting fields with many terms. Still in the
	  experimental phase

 * Make StorageRunner.main(), SummaSearcherRunner.main(), and
	  FilterControl.main() do a System.exit(1) if they encounter a fatal 
	  top level exception

 * Use 'set -e' in all Summix .sh script to have them bail out on
	  any uncaught errors

 * Make all Summix .sh shell scripts use 'exec' when launching their
	  primary child process. This way we don't litter 3 processes for
	  each service - we have one process/service and that is that of
	  the JVM.

 * Logging for Summix: Services now log to log/<service-type>.log
	  and log/<service-type>.fatal.log. All *-tool.sh log to
	  log/tools.log. Here <service-type> is derived from the basename of
	  the config file

Cheers,
Mikkel

[1]: http://sbdevel.wordpress.com/