would you check if your access key is the same as the one you see in
$pai app list
?
On Thu, Feb 16, 2017 at 9:47 AM Pat Ferrel wrote:
> Is the EventServer running?
>
>
> On Feb 16, 2017, at 9:01 AM, Сергей Купрюшин wrote:
>
> yes, i try that.
>
you can filter the data you need by using PEventStore API or modifying the
DataSource.scala. Then train different engine instance with different
configuration.
On Wed, Sep 7, 2016 at 4:57 PM, Donald Szeto wrote:
> Hi,
>
> If you are using the stock classification engine
I think the Java SDK already supports it creating events to a file, but
it's not documented.
https://github.com/PredictionIO/PredictionIO-Java-SDK/commit/6691144ebf1382aa1d060770a4fb7c0268f849d3
On Fri, Sep 9, 2016 at 7:59 AM, Pat Ferrel wrote:
> The page is now live
>
more details of how to use channel is here:
http://predictionio.incubator.apache.org/datacollection/channel/
there are some implementation here (segment, mailchimp)
https://github.com/apache/incubator-predictionio/tree/develop/data/src/main/scala/org/apache/predictionio/data/webhooks
basically
re: kappa vs lambda.
as far as i understand, at high-level, kappa is more like a subset of
lambda (ie. only keep the real-time part)
https://www.ericsson.com/research-blog/data-knowledge/data-processing-architectures-lambda-and-kappa/
Gerog, would you be more specific when you talk about "latency
You could add the price as "properties" of item.
Then modify the Query class to add 'price' as one of field
Modify isCandidate() function to take the price into account
On Tue, Jul 11, 2017 at 12:49 PM, Kenneth Chan <kenn...@apache.org> wrote:
> I think we are having wrong impression that every template are supposed to
> work together out of the box.
>
> The templates are meant to be examples and demonstration - that's why they
> are called templ
yes. HBase is currently supported, which seems similar to Accumulo.
it s not difficult to add another storage backend support option - just
need to implement the stroage layer interface. Contribution is welcome!
On Mon, Jul 10, 2017 at 8:54 AM Miller, Clifford <
it's all same set of events collected for my application and i can create
multiple engine to use these data for different purpose.
te from $set, $unset these
> streams can have db TTLs to age out old data for Lambda Engines. The system
> is always self-cleaning with no heavyweight operation required to keep just
> the right data (the db cleaner is heavyweight and slow), the data does not
> grow forever by design. This was never
thomas, if you always your own data store backend for events or your
application data, you don't have to use EventServer. Just implement a PIO
engine which directly reads from your data source.
On Thu, Jul 6, 2017 at 7:32 AM, Pat Ferrel wrote:
> The EventStore is
see here
https://spark.apache.org/docs/latest/mllib-ensembles.html#prediction
you can ask in Apache Spark's mailing list too.
On Fri, Jun 30, 2017 at 4:09 AM, Pat Ferrel wrote:
> You probably should ask on PredictionIO mailing list.
>
> Signup here:
ta problem, maybe other way is that the template should
also provide a "event validator" which can be loaded into event server and
advanced user can also customize it.
On Sat, Jul 8, 2017 at 12:31 AM, Kenneth Chan <kenn...@apache.org> wrote:
> # re: " I see it as
sk 0.0 in stage 3.0 (TID 9, localhost):
>> java.lang.NullPointerException
>>
>> Driver stacktrace:
>> at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$sch
>> eduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1431)
>> Caused by: java.
; shareable. Despite a lot of docs & discussion suggesting its share-ability,
> there is precious little documentation that presents how the multi-backend
> Storage really works in PIO. (I didn't understand it until I read a bunch
> of Storage source code.)
>
>
> From Kenneth Chan
15 matches
Mail list logo