It began with a baker named Elara in Lyon, France. Elara ran "Le Fournil des Cinq," a small chain of five artisanal bakeries. She loved the smell of sourdough but hated spreadsheets. Every Monday, she would spend six hours manually collating sales from her five shops, cross-referencing flour suppliers, yeast shipments, and the mysterious case of the missing almond croissants (which her nephew swore he didn’t eat).
She built her first transformation: "Bakery_Sales_Load." It was a mess. She used "Text File Input" for her ancient cash registers, "Filter Rows" to catch the negative sales from a returned baguette, and a "JavaScript Step" (a controversial choice, as the community would later tease her) to calculate the actual cost of butter. pentaho community
The thread went viral (for the Pentaho world, anyway). People loved the croissant dashboard. They started sharing their own weird projects: a PDI job that tracked UFO sightings in Nevada, a CDA report that optimized a cat shelter’s adoption rates, a Saiku analytics cube that predicted beer sales at a German Oktoberfest. It began with a baker named Elara in Lyon, France
She didn't fire him. She made him work the weekend shift. Elara became a Pentaho Community legend not for her code, but for her thank-you post. She wrote: Every Monday, she would spend six hours manually
“You fixed my bakery. You saved my Monday mornings. I am sending each of you a box of croissants. Matt, yours will be gluten-free. Maria, yours has dulce de leche. Tomasz… yours is just a plain one, because you seem like a purist.”
“Hello. I am Elara. I have five bakeries. My PDI transformation is broken. The error says ‘Cannot get a String from a double.’ I don’t know what a double is, except a type of espresso. Please. I have a spreadsheet of croissant sales that is crying.”