kbendick edited a comment on issue #2676: URL: https://github.com/apache/iceberg/issues/2676#issuecomment-854918867
> Ive seen some pretty involved docker and docker-compose demos that are cool but require a dozen docker images to be started locally. My request is that a new user don't have to start up half the world just to see how iceberg works, however maybe I am unique in that I find those types of demos frustrating. Maybe there is room for both too: quick, short, focused demos and a bigger integrated one to get a feel for waht its like to run in prod I agree. When myself and @rdblue were discussing this a while back, we wanted to keep things as simple as possible, particularly for the demo. So ideally just the bare mininum (a runtime, even if not distributed, and a catalog - ideally the simplest possible). I believe there are issues when using derby in memory (though possibly those have been corrected and I only recently reencountered them when using an older iceberg version). The setup I have is definitely more of a dev environment in that sense (3 or 4 images), but I'll see what I can do about getting it paired down. Once I've pushed the stuff I have early next week, we can go from there. I'm by no means married to the stuff I have currently, but do think it would be a good starting off point. I'll also take a look at the smoke tests etc in yours and see what can be done to help simplify mine. I agree that it might make sense to have both: something simple that people can just stand up without any nonsense, and then execute the basic Iceberg commands to get a feeling for what it's all about, as well as something that might be a bit more full featured (e.g. with Hive, etc) that people can look to to get an understanding of a more full setup. It would also allow for showing people in a more practical sense the various catalogs (i.e. something that runs with the Glue Catalog as well, etc). Perhaps some of it might be better suited for the wiki too, where a base setup that's slightly more complex might be desired. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
