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" <lewis.mcgibb...@gmail.com> 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 <starc...@umich.edu> 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 <javascript:;>> > > 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* >
