Index: src/docs/src/documentation/content/xdocs/notification.xml =================================================================== --- src/docs/src/documentation/content/xdocs/notification.xml (revision 1299332) +++ src/docs/src/documentation/content/xdocs/notification.xml (working copy) @@ -23,13 +23,13 @@ -

In HCatalog 2.0 we introduce notifications for certain events happening in the system. This way applications such as Oozie can wait for those events and schedule the work that depends on them. The current version of HCatalog supports two kinds of events:

+

HCatalog 0.2 provides notifications for certain events happening in the system. This way applications such as Oozie can wait for those events and schedule the work that depends on them. The current version of HCatalog supports two kinds of events:

-

No additional work is required to send a notification when a new partition is added: the existing addPartition call will send the notification message. This means that your existing code, when running with 0.2, will automatically send the notifications.

+

No additional work is required to send a notification when a new partition is added: the existing addPartition call will send the notification message.

Notification for a New Partition @@ -46,7 +46,7 @@

2. Subscribe to a topic you are interested in. When subscribing on a message bus, you need to subscribe to a particular topic to receive the messages that are being delivered on that topic.

Notification for a Set of Partitions +

Sometimes a user wants to wait until a collection of partitions is finished. For example, you may want to start processing after all partitions for a day are done. However, HCatalog has no notion of collections or hierarchies of partitions. To support this, HCatalog allows data writers to signal when they are finished writing a collection of partitions. Data readers may wait for this signal before beginning to read.

+

The example code below illustrates how to send a notification when a set of partitions has been added.

+

To signal, a data writer does this:

+ HiveMetaStoreClient msc = new HiveMetaStoreClient(conf); @@ -138,8 +142,8 @@ MapMessage mapMsg = (MapMessage)msg; Enumeration<String> keys = mapMsg.getMapNames(); - // Enumerate over all keys. This will print key value pairs specifying the particular partition - // which was marked done. In this case, it will print: + // Enumerate over all keys. This will print key-value pairs specifying the + // particular partition 44which was marked done. In this case, it will print: // date : 20110711 // country: *