Re: Schema Evolution within OODT CAS
Yeah I saw all the jars stuff whilst working through the list. From my side I'd certainly look to reuse rather than reimplemented where possible. On 22 Apr 2015 17:11, "Chris Mattmann" wrote: > No clue, but the CAS curator allows metadata update > through its REST services. I would be building on top > of those (and yes we need to uncouple the JAX-RS of those > services, along with the services that Ross Laidlaw wrote > that allow for querying, etc.) > > Turns out much of the stuff Tom Barber and you want Starch > to build the new whiz-bang UI is already there in the REST > layer - they are just coupled to the web apps and components > in some cases they support - note Paul Ramirez filed issues > before to uncouple them scope them out in JIRA. > > Cheers, > Chris > > > Chris Mattmann > chris.mattm...@gmail.com > > > > > -Original Message- > From: Michael Starch > Reply-To: > Date: Wednesday, April 22, 2015 at 10:55 AM > To: > Subject: Re: Schema Evolution within OODT CAS > > >There were proposals for a OODT Metadata update tool, which would fix this > >problem. Anyone know what happened to this work? > >On Apr 22, 2015 7:52 AM, "Lewis John Mcgibbney" > > > >wrote: > > > >> I get it... I've never used that backend however. > >> For every Catalog extending the base Catalog interface it is > >>implementation > >> specific. > >> Lucene catalog is Ok, Solr is not Etc > >> > >> On Wednesday, April 22, 2015, Michael Starch > wrote: > >> > >> > Lewis, > >> > > >> > In my experience, if the underlying catalog allows schema evolution, > >>so > >> > does OODT. > >> > > >> > Using the DataSourceCatalog meant our DBA could apply a schema update > >>to > >> > the database which was a form of schema evolution. > >> > > >> > Does this answer your question? > >> > > >> > Michael > >> > On Apr 22, 2015 7:40 AM, "Lewis John Mcgibbney" < > >> > lewis.mcgibb...@gmail.com > > >> > wrote: > >> > > >> > > hi Folks, > >> > > Very simple question... Is there any built in support for schema > >> > evolution > >> > > in OODT CAS? > >> > > Say I have product MD and the fundamental structure of the MD > >>changes > >> > (over > >> > > and above arbitrary changes in MD values) do I need to re catalog > >>all > >> of > >> > my > >> > > products? > >> > > Right now I think the answer is yes but would be pleasantly > >>surprised > >> to > >> > > hear otherwise. > >> > > Thanks > >> > > Lewis > >> > > > >> > > > >> > > -- > >> > > *Lewis* > >> > > > >> > > >> > >> > >> -- > >> *Lewis* > >> > > >
Re: Schema Evolution within OODT CAS
No clue, but the CAS curator allows metadata update through its REST services. I would be building on top of those (and yes we need to uncouple the JAX-RS of those services, along with the services that Ross Laidlaw wrote that allow for querying, etc.) Turns out much of the stuff Tom Barber and you want Starch to build the new whiz-bang UI is already there in the REST layer - they are just coupled to the web apps and components in some cases they support - note Paul Ramirez filed issues before to uncouple them scope them out in JIRA. Cheers, Chris Chris Mattmann chris.mattm...@gmail.com -Original Message- From: Michael Starch Reply-To: Date: Wednesday, April 22, 2015 at 10:55 AM To: Subject: Re: Schema Evolution within OODT CAS >There were proposals for a OODT Metadata update tool, which would fix this >problem. Anyone know what happened to this work? >On Apr 22, 2015 7:52 AM, "Lewis John Mcgibbney" > >wrote: > >> I get it... I've never used that backend however. >> For every Catalog extending the base Catalog interface it is >>implementation >> specific. >> Lucene catalog is Ok, Solr is not Etc >> >> On Wednesday, April 22, 2015, Michael Starch wrote: >> >> > Lewis, >> > >> > In my experience, if the underlying catalog allows schema evolution, >>so >> > does OODT. >> > >> > Using the DataSourceCatalog meant our DBA could apply a schema update >>to >> > the database which was a form of schema evolution. >> > >> > Does this answer your question? >> > >> > Michael >> > On Apr 22, 2015 7:40 AM, "Lewis John Mcgibbney" < >> > lewis.mcgibb...@gmail.com > >> > wrote: >> > >> > > hi Folks, >> > > Very simple question... Is there any built in support for schema >> > evolution >> > > in OODT CAS? >> > > Say I have product MD and the fundamental structure of the MD >>changes >> > (over >> > > and above arbitrary changes in MD values) do I need to re catalog >>all >> of >> > my >> > > products? >> > > Right now I think the answer is yes but would be pleasantly >>surprised >> to >> > > hear otherwise. >> > > Thanks >> > > Lewis >> > > >> > > >> > > -- >> > > *Lewis* >> > > >> > >> >> >> -- >> *Lewis* >>
Re: Schema Evolution within OODT CAS
Yeah right now the expectation is that if the metadata changes over time and it needs to be versioned, that the simple answer is that you simply record another product entry, with a new DataVersion, with new Metadata in an existing Catalog. HTH! Cheers, Chris Chris Mattmann chris.mattm...@gmail.com -Original Message- From: Lewis John Mcgibbney Reply-To: Date: Wednesday, April 22, 2015 at 10:40 AM To: "dev@oodt.apache.org" Subject: Schema Evolution within OODT CAS >hi Folks, >Very simple question... Is there any built in support for schema evolution >in OODT CAS? >Say I have product MD and the fundamental structure of the MD changes >(over >and above arbitrary changes in MD values) do I need to re catalog all of >my >products? >Right now I think the answer is yes but would be pleasantly surprised to >hear otherwise. >Thanks >Lewis > > >-- >*Lewis*
Re: Schema Evolution within OODT CAS
There were proposals for a OODT Metadata update tool, which would fix this problem. Anyone know what happened to this work? On Apr 22, 2015 7:52 AM, "Lewis John Mcgibbney" wrote: > I get it... I've never used that backend however. > For every Catalog extending the base Catalog interface it is implementation > specific. > Lucene catalog is Ok, Solr is not Etc > > On Wednesday, April 22, 2015, Michael Starch wrote: > > > Lewis, > > > > In my experience, if the underlying catalog allows schema evolution, so > > does OODT. > > > > Using the DataSourceCatalog meant our DBA could apply a schema update to > > the database which was a form of schema evolution. > > > > Does this answer your question? > > > > Michael > > On Apr 22, 2015 7:40 AM, "Lewis John Mcgibbney" < > > lewis.mcgibb...@gmail.com > > > wrote: > > > > > hi Folks, > > > Very simple question... Is there any built in support for schema > > evolution > > > in OODT CAS? > > > Say I have product MD and the fundamental structure of the MD changes > > (over > > > and above arbitrary changes in MD values) do I need to re catalog all > of > > my > > > products? > > > Right now I think the answer is yes but would be pleasantly surprised > to > > > hear otherwise. > > > Thanks > > > Lewis > > > > > > > > > -- > > > *Lewis* > > > > > > > > -- > *Lewis* >
Re: Schema Evolution within OODT CAS
I get it... I've never used that backend however. For every Catalog extending the base Catalog interface it is implementation specific. Lucene catalog is Ok, Solr is not Etc On Wednesday, April 22, 2015, Michael Starch wrote: > Lewis, > > In my experience, if the underlying catalog allows schema evolution, so > does OODT. > > Using the DataSourceCatalog meant our DBA could apply a schema update to > the database which was a form of schema evolution. > > Does this answer your question? > > Michael > On Apr 22, 2015 7:40 AM, "Lewis John Mcgibbney" < > lewis.mcgibb...@gmail.com > > wrote: > > > hi Folks, > > Very simple question... Is there any built in support for schema > evolution > > in OODT CAS? > > Say I have product MD and the fundamental structure of the MD changes > (over > > and above arbitrary changes in MD values) do I need to re catalog all of > my > > products? > > Right now I think the answer is yes but would be pleasantly surprised to > > hear otherwise. > > Thanks > > Lewis > > > > > > -- > > *Lewis* > > > -- *Lewis*
Re: Schema Evolution within OODT CAS
Lewis, In my experience, if the underlying catalog allows schema evolution, so does OODT. Using the DataSourceCatalog meant our DBA could apply a schema update to the database which was a form of schema evolution. Does this answer your question? Michael On Apr 22, 2015 7:40 AM, "Lewis John Mcgibbney" wrote: > hi Folks, > Very simple question... Is there any built in support for schema evolution > in OODT CAS? > Say I have product MD and the fundamental structure of the MD changes (over > and above arbitrary changes in MD values) do I need to re catalog all of my > products? > Right now I think the answer is yes but would be pleasantly surprised to > hear otherwise. > Thanks > Lewis > > > -- > *Lewis* >
Schema Evolution within OODT CAS
hi Folks, Very simple question... Is there any built in support for schema evolution in OODT CAS? Say I have product MD and the fundamental structure of the MD changes (over and above arbitrary changes in MD values) do I need to re catalog all of my products? Right now I think the answer is yes but would be pleasantly surprised to hear otherwise. Thanks Lewis -- *Lewis*
