FYI- I haven't actually tried this, but I think it should work. If
__package doesn't work, try without the __package/ prefix (i.e.
fopen('yourfile.txt')).
On Tue, Mar 24, 2015 at 1:26 PM, Chris Riccomini
wrote:
> Cool, that should work. In YARN, the .tgz file is unzipped into
> $CWD/__package/,
Cool, that should work. In YARN, the .tgz file is unzipped into
$CWD/__package/, so if you have a file in the root of your tarball, then
fopen('__package/yourfile.txt') should work.
On Tue, Mar 24, 2015 at 1:22 PM, Shekar Tippur wrote:
> Thanks Chris. I was trying option #2.
>
> - Shekar
>
> On
Thanks Chris. I was trying option #2.
- Shekar
On Tue, Mar 24, 2015 at 11:09 AM, Chris Riccomini
wrote:
> Hey Shekar,
>
> So you have two properties files? One is the Samza job file, and the other
> is one with the format you described above?
>
> Several options:
>
> 1. Move these properties in
Hey Shekar,
So you have two properties files? One is the Samza job file, and the other
is one with the format you described above?
Several options:
1. Move these properties into the main Samza job file. You'll then have
access to them via the Config object.
2. Put the property file into your .tg
I would like to decouple Samza properties with the custom ones (if
possible).
- Shekar
On Mon, Mar 23, 2015 at 3:12 PM, Shekar Tippur wrote:
> Hello,
>
> I have a custom properties file with name value pairs.
>
> name1 value1
> name2 value2
> name3 value3
>
> I want to pass this to Yarn job. Wh
