that could indeed lead to problems in my IoT scenario.. Thanks for filing.
-----Original Message----- From: Claus Ibsen <claus.ib...@gmail.com> Sent: Monday, April 29, 2019 7:48 AM To: users@camel.apache.org Subject: Re: [solved] camel-azure: syntax for setting blobnames dynamically when uploading files to BlockBlob ? Hi Ah yeah using toD can help resolve this, but mind if you have many unique file names, you end up creating many endpoints. We should also allow to specify a header with the blob name, then we can use the same endpoint but let the header override the blob name. I logged a ticket https://issues.apache.org/jira/browse/CAMEL-13462 On Thu, Apr 25, 2019 at 5:35 PM Marx, Peter <peter.m...@knorr-bremse.com> wrote: > > I found the solution myself in CiA, 2nd edition (which arrived today, > replacing my 1st edition now..), in chapter 2.5.1. > > Using .toD instead .to, Simple expressions are evaluated: > > from("file:c:\\mx\\source?delete=true") > .toD("azure-blob://shared1/mxtest/{ > ${file:onlyname}?credentials=#credsreg&operation=updateBlockBlob"); > > sets the name of the created blob to the filename of the source file. > > Peter > > > > -----Original Message----- > From: Marx, Peter <peter.m...@knorr-bremse.com> > Sent: Tuesday, April 23, 2019 2:49 PM > To: users@camel.apache.org > Subject: camel-azure: syntax for setting blobnames dynamically when uploading > files to BlockBlob ? > > I want to upload 1-n files to Azure BlockBlob storage with camel-azure > 2.23.0, but can't figure out the right syntax from the docs. > > The resulting blobs should have e.g the same name as the files in the source > folders. > > Container exists (mxtest). When I set the blobname like below, the resulting > blob has of course the content of the file which was uploadad last: > > from("file:c:\\mx\\source?delete=true") > .to("azure-blob://shared1/mxtest/blobname?credentials=#credsreg&operat > ion=updateBlockBlob"); > > How can I inject the filename found by "from" into the URI of ".to" ? > > > Peter > > Knorr-Bremse Systeme für Schienenfahrzeuge GmbH > Sitz: München > Geschäftsführer: Dr. Jürgen Wilder (Vorsitzender), Mark Cleobury, Dr. > Nicolas Lange, Dr. Peter Radina, Harald Schneider Vorsitzender des > Aufsichtsrats: Klaus Deller Registergericht München, HR B 91 181 > > This transmission is intended solely for the addressee and contains > confidential information. > If you are not the intended recipient, please immediately inform the sender > and delete the message and any attachments from your system. > Furthermore, please do not copy the message or disclose the contents to > anyone unless agreed otherwise. To the extent permitted by law we shall in no > way be liable for any damages, whatever their nature, arising out of > transmission failures, viruses, external influence, delays and the like. > > > Knorr-Bremse Systeme für Schienenfahrzeuge GmbH > Sitz: München > Geschäftsführer: Dr. Jürgen Wilder (Vorsitzender), Mark Cleobury, Dr. > Nicolas Lange, Dr. Peter Radina, Harald Schneider Vorsitzender des > Aufsichtsrats: Klaus Deller Registergericht München, HR B 91 181 > > This transmission is intended solely for the addressee and contains > confidential information. > If you are not the intended recipient, please immediately inform the sender > and delete the message and any attachments from your system. > Furthermore, please do not copy the message or disclose the contents to > anyone unless agreed otherwise. To the extent permitted by law we shall in no > way be liable for any damages, whatever their nature, arising out of > transmission failures, viruses, external influence, delays and the like. > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2 Knorr-Bremse Systeme für Schienenfahrzeuge GmbH Sitz: München Geschäftsführer: Dr. Jürgen Wilder (Vorsitzender), Mark Cleobury, Dr. Nicolas Lange, Dr. Peter Radina, Harald Schneider Vorsitzender des Aufsichtsrats: Klaus Deller Registergericht München, HR B 91 181 This transmission is intended solely for the addressee and contains confidential information. If you are not the intended recipient, please immediately inform the sender and delete the message and any attachments from your system. Furthermore, please do not copy the message or disclose the contents to anyone unless agreed otherwise. To the extent permitted by law we shall in no way be liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.
