Should we create a branch for ODM development? I feel that there are several steps that need to happen before it’s in the master.
1. contribution of database creation scripts 2. possible component (ingest, ml and oa) changes/additions for said databases 3. documentation changes any thoughts? - Nathanael > On Apr 26, 2017, at 8:50 AM, Cesar B <[email protected]> wrote: > > Hello @Morris and @Jon > > Please refer to the process below: > > http://spot.apache.org/community/contribute/ > > Getting this into the project repo will be awesome, Community in general has > been looking to play with ODM for a while. > > Thanks, > Cesar > > > On April 26, 2017 at 8:07:10 AM, [email protected] ([email protected]) wrote: > > I totally agree - I would love something to align my data against, and have > been waiting on a (documented) standard to emerge. > > Jon > > On Wed, Apr 26, 2017 at 8:16 AM Morris Hicks <[email protected]> wrote: > >> Scripts have been created for automating the creation of the open data >> model and enabling fast data ingest & query as outlined in this cloudera >> blog. >> < >> https://blog.cloudera.com/blog/2015/11/how-to-ingest-and-query-fast-data-with-impala-without-kudu/ >> >>> >> It could be beneficial to publish this content to the project GitHub to >> allow org's to start using the open data model. What's the recommended >> mechanism to serve this content (create a new branch, create a >> subdirectory in existing branch, etc.)? >> >> Thanks, >> >> -- >> Morris Hicks >> Strategic Enablement Expert, Cloudera >> [email protected] >> (703) 447-5883 >> > -- > > Jon
