IP Library › Granted Patent US 9,141,681
Granted Patent B2
US 9,141,681 · App. 13/688,698 · Granted Sep 22, 2015

Creating a column family in a database

Inventors: Filip Nguyen (Brno, CZ); Filip Elias (Vysni Lhoty, CZ)
Assignee: Red Hat, Inc.
G06F17/30575G06F17/30566G06F17/30578
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,141,681
App. No.
13/688,698
Granted
Sep 22, 2015
Kind
B2
Abstract

A mechanism for providing messages for Java message service (JMS). A method includes receiving, by a Java message service (JMS) server executed by a processing device, key-value data pair. The key-value data pair is sent by a client. The method also includes extracting, by the processing device, destination information of a JMS message from the value data of the key-value data pair. The destination information is either a JMS queue or a JMS topic. The method further includes storing, by the processing device, the key-value data pair in a column family of not only structured query language (NoSQL) database when one of the JMS queue or the JMS topic associated with the received key-value data pair exists in the column family of the NoSQL database. The column family includes a plurality of stored key-value data pairs.

Claims (50)

1. A method comprising:

receiving, by a processing device, a key-value data pair from a client;

extracting, by the processing device, destination information of a JAVA™ message service (JMS) message from value data of the key-value data pair, wherein the destination information is one of a JMS queue or a JMS topic associated with the received key-value data pair; and

when one of the JMS queue or the JMS topic associated with the received key-value data pair exists in a column family of not only structured query language (NoSQL) database of the JMS server, storing, by the processing device, the key-value data pair in the column family of the NoSQL database, wherein the column family comprising a plurality of stored key-value data pairs.

2. The method of claim 1 , further comprising when one of the JMS queue or the JMS topic associated with the key-value data pair does not exists in the column family of the NoSQL database, creating a column family in the NoSQL database and storing the received key-value data pair in the column family.

3. The method of claim 1 wherein the JMS message is converted into the key-value data pair by the client.

4. The method of claim 1 wherein the JMS message is one of generated or received by the client.

5. The method of claim 1 further comprising

receiving a request to retrieve the key-value data pair associated with the JMS queue; and

retrieving the key-value data pair associated with the JMS queue, wherein the key-value data pair associated with the JMS queue is retrieved from the column family of the NoSQL database.

6. The method of claim 1 , further comprising sending the retrieved key-value data pair associated with the JMS queue to the client.

7. The method of claim 1 further comprising receiving a request to subscribe to the JMS topic; and

creating a column family of the key-value data pairs in the NosQL database, wherein the column family comprises the JMS topic for the client subscribed to the JMS topic.

8. The method of claim 7 further comprising:

receiving a second key-value data pair associated with the JMS topic; and

replicating the second key-value data pair in the column family of the NoSQL database subscribing to the JMS topic.

9. The method of claim 8 , further compromising sending the replicated key-value data pair to the client subscribed to the JMS topic.

10. A system comprising:

a memory;

a processing device, operatively coupled to the memory, to:

receive, from a client, a key-value data pair;

extract destination information of a JAVA™ message service (JMS) message from value data of the key-value data pair, wherein the destination information is one of a JMS queue associated with the received key-value data pair; and

when one of the JMS queue or the JMS topic associated with the received key-value data pair exists in a column family of the NoSQL database, store the key-value data pair in the column family of the NoSQL database, wherein the column family comprising a plurality of stored key-value data pairs.

11. The system of claim 10 the processing device further to:

create a column family in the NoSQL database; and

store the received key-value data pair in the column family when one of the JMS queue or the JMS topic associated with key-value data pair does not exist in the NoSQL database.

12. The system of claim 10 , the processing device further to:

receive a request to retrieve the key-value data pair associated with the JMS queue; and

retrieve the key-value data pair associated with the JMS queue, wherein the key-value data pair associated with the JMS queue is retrieved from the column family of the NoSQL database.

13. The system of claim 10 the processing device further to:

receive a request to subscribe to the JMS topic; and

create a column family of the key-value data pairs in the NosQL database, wherein the column family comprises the JMS topic for the client subscribed to the JMS topic.

14. The system of claim 13 , the processing device further to:

receive a second key-value data pair associated with the JMS topic; and

replicate the second key-value data pair in the column family of the NoSQL database subscribing to the JMS topic; and send the replicated key-value data pair to the client subscribed to the JMS topic.

15. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to:

receive a key-value data pair from a client;

extract destination information of a JAVA™ message service (JMS) message from value data of the key-value data pair, wherein the destination information is one of a JMS queue or a JMS topic associated with the received key-value data pair; and

when one of the JMS queue or the JMS topic associated with the received key-value data pair exists in a column family of not only structured query language (NoSQL) database of the JMS server, store the key-value data pair in the column family of the NoSQL database, wherein the column family comprising a plurality of stored key-value data pairs.

16. The non-transitory machine-readable storage medium of claim 15 , the processing device further to:

when one of the JMS queue or the JMS topic associated with the key-value data pair does not exists in the column family of the NoSQL database, create a column family in the NoSQL database and store the received key-value data pair in the column family.

17. The non-transitory machine-readable storage medium of claim 15 , the processing device further to:

receive a request to retrieve the key-value data pair associated with the JMS queue; and

retrieve the key-value data pair associated with the JMS queue, wherein the key-value data pair associated with the JMS queue is retrieved from the column family of the NoSQL database.

18. The non-transitory machine-readable storage medium of claim 15 , the processing device further to:

receive a request to subscribe to the JMS topic; and

create a column family of the key-value data pairs in the NosQL database, wherein the column family comprises the JMS topic for the client subscribed to the JMS topic.

19. The non-transitory machine-readable storage medium of claim 18 , the processing device further to:

receive a second key-value data pair associated with the JMS topic; and

replicate the second key-value data pair in the column family of the NoSQL database subscribing to the JMS topic.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2012
From: NGUYEN, FILIP; ELIAS, FILIP
To: RED HAT, INC.
Reel/Frame 029375/0791 →
Continuity (1)
Related Publication 20140149452A1 · May 29, 2014