You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fluo.apache.org by Alan Camillo <al...@blueshift.com.br> on 2018/02/15 00:43:03 UTC
ExportQueue
Hello guys!
Simple questions:
How do to use the exportqueue recipe through command “fluo init...”?
There’s a comment on examples saying:
/**
* Call this method before initializing Fluo.
*
* @param fluoConfig the configuration object that will be used to initialize Fluo
*/
Is this mean recipes just work through main methods? If so, is possible initialize a fluo application without call the “fluo init” command?
If I provide the export queue properties on fluo-app.properties can I jump this step?
Last question!
Do the recipes work on fluo 1.2?
Thanks!!
Re: ExportQueue
Posted by Keith Turner <ke...@deenlo.com>.
On Thu, Feb 15, 2018 at 4:41 PM, Mike Walch <mw...@gmail.com> wrote:
> Hi Alan,
>
> I assume you are referring to the preInit() method in the documentation
> below:
>
> https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/export-queue/
>
> Yes, this should be called in a Main method before initializing Fluo. You
> can still initialize Fluo using "fluo init" command but you could also
> initalize Fluo using the Fluo API. Below is example main method that does
There is a problem with initializing from the API in 1.1.0, it will
not set up Fluo's server side code that runs in Accumulo tablet
servers. Running Fluo init does set this up in the bash scripts.
This is fixed for 1.2, it was moved from bash to java code. So in 1.2
the API and the command line both set this up.
> everything:
>
> https://github.com/astralway/webindex/blob/master/modules/integration/src/main/java/webindex/integration/DevServer.java
>
> In the example, the export queue is configured in
> env.configureApplication(config,
> config);
> The 1.1.0-incubating recipes should work with fluo 1.2.
>
> Let me know if you have any other questions!
> -Mike
>
> On Wed, Feb 14, 2018 at 7:43 PM, Alan Camillo <al...@blueshift.com.br> wrote:
>
>> Hello guys!
>> Simple questions:
>>
>> How do to use the exportqueue recipe through command “fluo init...”?
>>
>> There’s a comment on examples saying:
>> /**
>> * Call this method before initializing Fluo.
>> *
>> * @param fluoConfig the configuration object that will be used to
>> initialize Fluo
>> */
>>
>> Is this mean recipes just work through main methods? If so, is possible
>> initialize a fluo application without call the “fluo init” command?
>>
>> If I provide the export queue properties on fluo-app.properties can I jump
>> this step?
>>
>> Last question!
>> Do the recipes work on fluo 1.2?
>>
>> Thanks!!
>>
Re: ExportQueue
Posted by Alan Camillo <al...@blueshift.com.br>.
Actually I was thinking about transform the Observer Providers in
annotations too.
One class less to write for observer.
For the traditional ones we could provide a disable annotation search flag
in fluo-app.properties.
Thank you Keith!
Alan Camillo
*BlueShift *I IT Director
Cel.: +55 11 98283-6358
Tel.: +55 11 4605-5082
2018-02-16 5:33 GMT-02:00 Keith Turner <ke...@deenlo.com>:
> On Thu, Feb 15, 2018 at 5:46 PM, Alan Camillo <al...@blueshift.com.br>
> wrote:
> > Thank you Mike!
> > Actually I was able to execute the queue and the accumulo exporter but I
> > had to remove some dependencies from the recipe import to execute on 1.2
> > version:
> >
> > <dependency>
> > <groupId>org.apache.fluo</groupId>
> > <artifactId>fluo-recipes-accumulo</artifactId>
> > <version>1.2.0-SNAPSHOT</version>
> > <exclusions>
> > <exclusion>
> > <groupId>log4j</groupId>
> > <artifactId>log4j</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>org.slf4j</groupId>
> > <artifactId>slf4j-log4j12</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>org.apache.fluo</groupId>
> > <artifactId>fluo-api</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>org.apache.fluo</groupId>
> > <artifactId>fluo-core</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>org.apache.zookeeper</groupId>
> > <artifactId>zookeeper</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>org.apache.accumulo</groupId>
> > <artifactId>accumulo-core</artifactId>
> > </exclusion>
> > </exclusions>
> > </dependency>
> > <dependency>
> > <groupId>org.apache.accumulo</groupId>
> > <artifactId>accumulo-core</artifactId>
> > <version>1.8.1</version>
> > <scope>*provided*</scope>
> > </dependency>
> >
> > While I didn't exclude this dependencies it didn't work.
>
> I am not sure what is going on here. I will look into this to see if
> we did anything in 1.2 that causes problems with recipes.
>
> >
> > About the *preInit *method used to configure the export queue on the
> > example, should we think about a specific class the execute this kind of
> > operations? Like a observer but different.
>
> So you are thinking Fluo could scan classes looking for a certain
> annotations and executing those classes at init time? That is an
> interesting idea.
>
> > The Spring introduced an annotation called " @PostConstruct " to execute
> > code after the application bootstrap but before the programmer's logic.
> >
> > @PostConstruct
> > public void init() {
> > // any code
> > }
> >
> > Thanks!
> >
> > Alan Camillo
> > *BlueShift *I IT Director
> > Cel.: +55 11 98283-6358
> > Tel.: +55 11 4605-5082
> >
> > 2018-02-15 19:41 GMT-02:00 Mike Walch <mw...@gmail.com>:
> >
> >> Hi Alan,
> >>
> >> I assume you are referring to the preInit() method in the documentation
> >> below:
> >>
> >> https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/
> export-queue/
> >>
> >> Yes, this should be called in a Main method before initializing Fluo.
> You
> >> can still initialize Fluo using "fluo init" command but you could also
> >> initalize Fluo using the Fluo API. Below is example main method that
> does
> >> everything:
> >>
> >> https://github.com/astralway/webindex/blob/master/modules/
> >> integration/src/main/java/webindex/integration/DevServer.java
> >>
> >> In the example, the export queue is configured in
> >> env.configureApplication(config,
> >> config);
> >> The 1.1.0-incubating recipes should work with fluo 1.2.
> >>
> >> Let me know if you have any other questions!
> >> -Mike
> >>
> >> On Wed, Feb 14, 2018 at 7:43 PM, Alan Camillo <al...@blueshift.com.br>
> >> wrote:
> >>
> >> > Hello guys!
> >> > Simple questions:
> >> >
> >> > How do to use the exportqueue recipe through command “fluo init...”?
> >> >
> >> > There’s a comment on examples saying:
> >> > /**
> >> > * Call this method before initializing Fluo.
> >> > *
> >> > * @param fluoConfig the configuration object that will be used to
> >> > initialize Fluo
> >> > */
> >> >
> >> > Is this mean recipes just work through main methods? If so, is
> possible
> >> > initialize a fluo application without call the “fluo init” command?
> >> >
> >> > If I provide the export queue properties on fluo-app.properties can I
> >> jump
> >> > this step?
> >> >
> >> > Last question!
> >> > Do the recipes work on fluo 1.2?
> >> >
> >> > Thanks!!
> >> >
> >>
>
Re: ExportQueue
Posted by Keith Turner <ke...@deenlo.com>.
On Thu, Feb 15, 2018 at 5:46 PM, Alan Camillo <al...@blueshift.com.br> wrote:
> Thank you Mike!
> Actually I was able to execute the queue and the accumulo exporter but I
> had to remove some dependencies from the recipe import to execute on 1.2
> version:
>
> <dependency>
> <groupId>org.apache.fluo</groupId>
> <artifactId>fluo-recipes-accumulo</artifactId>
> <version>1.2.0-SNAPSHOT</version>
> <exclusions>
> <exclusion>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-log4j12</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.fluo</groupId>
> <artifactId>fluo-api</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.fluo</groupId>
> <artifactId>fluo-core</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.zookeeper</groupId>
> <artifactId>zookeeper</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.accumulo</groupId>
> <artifactId>accumulo-core</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.accumulo</groupId>
> <artifactId>accumulo-core</artifactId>
> <version>1.8.1</version>
> <scope>*provided*</scope>
> </dependency>
>
> While I didn't exclude this dependencies it didn't work.
I am not sure what is going on here. I will look into this to see if
we did anything in 1.2 that causes problems with recipes.
>
> About the *preInit *method used to configure the export queue on the
> example, should we think about a specific class the execute this kind of
> operations? Like a observer but different.
So you are thinking Fluo could scan classes looking for a certain
annotations and executing those classes at init time? That is an
interesting idea.
> The Spring introduced an annotation called " @PostConstruct " to execute
> code after the application bootstrap but before the programmer's logic.
>
> @PostConstruct
> public void init() {
> // any code
> }
>
> Thanks!
>
> Alan Camillo
> *BlueShift *I IT Director
> Cel.: +55 11 98283-6358
> Tel.: +55 11 4605-5082
>
> 2018-02-15 19:41 GMT-02:00 Mike Walch <mw...@gmail.com>:
>
>> Hi Alan,
>>
>> I assume you are referring to the preInit() method in the documentation
>> below:
>>
>> https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/export-queue/
>>
>> Yes, this should be called in a Main method before initializing Fluo. You
>> can still initialize Fluo using "fluo init" command but you could also
>> initalize Fluo using the Fluo API. Below is example main method that does
>> everything:
>>
>> https://github.com/astralway/webindex/blob/master/modules/
>> integration/src/main/java/webindex/integration/DevServer.java
>>
>> In the example, the export queue is configured in
>> env.configureApplication(config,
>> config);
>> The 1.1.0-incubating recipes should work with fluo 1.2.
>>
>> Let me know if you have any other questions!
>> -Mike
>>
>> On Wed, Feb 14, 2018 at 7:43 PM, Alan Camillo <al...@blueshift.com.br>
>> wrote:
>>
>> > Hello guys!
>> > Simple questions:
>> >
>> > How do to use the exportqueue recipe through command “fluo init...”?
>> >
>> > There’s a comment on examples saying:
>> > /**
>> > * Call this method before initializing Fluo.
>> > *
>> > * @param fluoConfig the configuration object that will be used to
>> > initialize Fluo
>> > */
>> >
>> > Is this mean recipes just work through main methods? If so, is possible
>> > initialize a fluo application without call the “fluo init” command?
>> >
>> > If I provide the export queue properties on fluo-app.properties can I
>> jump
>> > this step?
>> >
>> > Last question!
>> > Do the recipes work on fluo 1.2?
>> >
>> > Thanks!!
>> >
>>
Re: ExportQueue
Posted by Alan Camillo <al...@blueshift.com.br>.
Thank you Mike!
Actually I was able to execute the queue and the accumulo exporter but I
had to remove some dependencies from the recipe import to execute on 1.2
version:
<dependency>
<groupId>org.apache.fluo</groupId>
<artifactId>fluo-recipes-accumulo</artifactId>
<version>1.2.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.fluo</groupId>
<artifactId>fluo-api</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.fluo</groupId>
<artifactId>fluo-core</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.zookeeper</groupId>
<artifactId>zookeeper</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.accumulo</groupId>
<artifactId>accumulo-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.accumulo</groupId>
<artifactId>accumulo-core</artifactId>
<version>1.8.1</version>
<scope>*provided*</scope>
</dependency>
While I didn't exclude this dependencies it didn't work.
About the *preInit *method used to configure the export queue on the
example, should we think about a specific class the execute this kind of
operations? Like a observer but different.
The Spring introduced an annotation called " @PostConstruct " to execute
code after the application bootstrap but before the programmer's logic.
@PostConstruct
public void init() {
// any code
}
Thanks!
Alan Camillo
*BlueShift *I IT Director
Cel.: +55 11 98283-6358
Tel.: +55 11 4605-5082
2018-02-15 19:41 GMT-02:00 Mike Walch <mw...@gmail.com>:
> Hi Alan,
>
> I assume you are referring to the preInit() method in the documentation
> below:
>
> https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/export-queue/
>
> Yes, this should be called in a Main method before initializing Fluo. You
> can still initialize Fluo using "fluo init" command but you could also
> initalize Fluo using the Fluo API. Below is example main method that does
> everything:
>
> https://github.com/astralway/webindex/blob/master/modules/
> integration/src/main/java/webindex/integration/DevServer.java
>
> In the example, the export queue is configured in
> env.configureApplication(config,
> config);
> The 1.1.0-incubating recipes should work with fluo 1.2.
>
> Let me know if you have any other questions!
> -Mike
>
> On Wed, Feb 14, 2018 at 7:43 PM, Alan Camillo <al...@blueshift.com.br>
> wrote:
>
> > Hello guys!
> > Simple questions:
> >
> > How do to use the exportqueue recipe through command “fluo init...”?
> >
> > There’s a comment on examples saying:
> > /**
> > * Call this method before initializing Fluo.
> > *
> > * @param fluoConfig the configuration object that will be used to
> > initialize Fluo
> > */
> >
> > Is this mean recipes just work through main methods? If so, is possible
> > initialize a fluo application without call the “fluo init” command?
> >
> > If I provide the export queue properties on fluo-app.properties can I
> jump
> > this step?
> >
> > Last question!
> > Do the recipes work on fluo 1.2?
> >
> > Thanks!!
> >
>
Re: ExportQueue
Posted by Mike Walch <mw...@gmail.com>.
Hi Alan,
I assume you are referring to the preInit() method in the documentation
below:
https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/export-queue/
Yes, this should be called in a Main method before initializing Fluo. You
can still initialize Fluo using "fluo init" command but you could also
initalize Fluo using the Fluo API. Below is example main method that does
everything:
https://github.com/astralway/webindex/blob/master/modules/integration/src/main/java/webindex/integration/DevServer.java
In the example, the export queue is configured in
env.configureApplication(config,
config);
The 1.1.0-incubating recipes should work with fluo 1.2.
Let me know if you have any other questions!
-Mike
On Wed, Feb 14, 2018 at 7:43 PM, Alan Camillo <al...@blueshift.com.br> wrote:
> Hello guys!
> Simple questions:
>
> How do to use the exportqueue recipe through command “fluo init...”?
>
> There’s a comment on examples saying:
> /**
> * Call this method before initializing Fluo.
> *
> * @param fluoConfig the configuration object that will be used to
> initialize Fluo
> */
>
> Is this mean recipes just work through main methods? If so, is possible
> initialize a fluo application without call the “fluo init” command?
>
> If I provide the export queue properties on fluo-app.properties can I jump
> this step?
>
> Last question!
> Do the recipes work on fluo 1.2?
>
> Thanks!!
>