You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Jonathan Robie <jo...@redhat.com> on 2009/10/07 15:22:58 UTC
Plugging in SQL-based stores
What approach are you taking to make it straightforward to plug in a
given SQL-based store?
Jonathan
David Ingham wrote:
> The way Steve is approaching the SQL-based store is to separate out common code, that would apply to all SQL-based stores, from the specifics of a particular database implementation. We're focusing on Microsoft SQL Server initially but the hope is that it would be straightforward to plug in another database, such as SQLite. Thanks to Carl and the Red Hat guys for providing the original BDB code that was used as the basis of this work.
>
> Dave.
>
> -----Original Message-----
> From: Aidan Skinner [mailto:aidan@apache.org]
> Sent: Monday, October 05, 2009 2:13 PM
> To: dev@qpid.apache.org
> Subject: Re: Opportunity: 0.6 Release Manager - C++ Volunteers
>
> On Fri, Oct 2, 2009 at 7:01 PM, David Ingham <Da...@microsoft.com> wrote:
>
>> Hi Marnie,
>>
>> On the Windows side, we'd like to get see the following items in 0.6:
>>
>> * Steve's refactoring of the C++ message store with support for Microsoft SQL Server
>> (https://issues.apache.org/jira/browse/QPID-1726)
>>
>
> This is going into SQL Server? It'd be cool if we could have a similar
> schema etc. as the Derby store. I hadn't realised that it depended on
> outside components, just kinda assumed that it'd be self-contained.
>
> - Aidan
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Plugging in SQL-based stores
Posted by Steve Huston <sh...@riverace.com>.
Hi Aidan,
> On Wed, Oct 7, 2009 at 4:39 PM, Steve Huston
> <sh...@riverace.com> wrote:
>
> > The way this has shaped up (and I'll be posting code soon) is that
> > there are two layers of plug-in: the portable store and the
> > storage-specific backend. The portable store offers an option to
> > select the backend, validates requests from the broker, and
directs
> > the recovery; the backend knows the storage layout and
> manages it. Any
> > kind of storage can plug into the backend, SQL or otherwise.
>
> Did you end up seperating the message store stuff from the
> configuration data?
No - the config info is in a different table, but in the same database
as the messaging info.
> It's something we've been looking into doing for
> the Java broker for a while. If this is going to land for 0.6 I'd
> really appreciate getting a look at it sooner rather than later so
we
> can try to figure out a compatible schema...
The code should be available today or tomorrow. The Windows
implementation is scheduled for inclusion in 0.6. I can't speak to any
plans on the Linux implementation.
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Plugging in SQL-based stores
Posted by Aidan Skinner <ai...@gmail.com>.
On Wed, Oct 7, 2009 at 4:39 PM, Steve Huston <sh...@riverace.com> wrote:
> The way this has shaped up (and I'll be posting code soon) is that
> there are two layers of plug-in: the portable store and the
> storage-specific backend. The portable store offers an option to
> select the backend, validates requests from the broker, and directs
> the recovery; the backend knows the storage layout and manages it. Any
> kind of storage can plug into the backend, SQL or otherwise.
Did you end up seperating the message store stuff from the
configuration data? It's something we've been looking into doing for
the Java broker for a while. If this is going to land for 0.6 I'd
really appreciate getting a look at it sooner rather than later so we
can try to figure out a compatible schema...
- Aidan
--
Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org
"A witty saying proves nothing" - Voltaire
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Plugging in SQL-based stores
Posted by Steve Huston <sh...@riverace.com>.
Hi Jonathan,
> -----Original Message-----
> From: Jonathan Robie [mailto:jonathan.robie@redhat.com]
>...
> What approach are you taking to make it straightforward to plug in a
> given SQL-based store?
The way this has shaped up (and I'll be posting code soon) is that
there are two layers of plug-in: the portable store and the
storage-specific backend. The portable store offers an option to
select the backend, validates requests from the broker, and directs
the recovery; the backend knows the storage layout and manages it. Any
kind of storage can plug into the backend, SQL or otherwise.
-Steve
> David Ingham wrote:
> > The way Steve is approaching the SQL-based store is to
> separate out common code, that would apply to all SQL-based
> stores, from the specifics of a particular database
> implementation. We're focusing on Microsoft SQL Server
> initially but the hope is that it would be straightforward to
> plug in another database, such as SQLite. Thanks to Carl and
> the Red Hat guys for providing the original BDB code that was
> used as the basis of this work.
> >
> > Dave.
> >
> > -----Original Message-----
> > From: Aidan Skinner [mailto:aidan@apache.org]
> > Sent: Monday, October 05, 2009 2:13 PM
> > To: dev@qpid.apache.org
> > Subject: Re: Opportunity: 0.6 Release Manager - C++ Volunteers
> >
> > On Fri, Oct 2, 2009 at 7:01 PM, David Ingham
> <Da...@microsoft.com> wrote:
> >
> >> Hi Marnie,
> >>
> >> On the Windows side, we'd like to get see the following
> items in 0.6:
> >>
> >> * Steve's refactoring of the C++ message store with
> support for Microsoft SQL Server
> >> (https://issues.apache.org/jira/browse/QPID-1726)
> >>
> >
> > This is going into SQL Server? It'd be cool if we could
> have a similar
> > schema etc. as the Derby store. I hadn't realised that it
> depended on
> > outside components, just kinda assumed that it'd be
self-contained.
> >
> > - Aidan
> >
>
>
>
---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org