Oh, Ok. That's my mistake then. I think creating a new app would solve the
problem.
Thanks
On Wed, Apr 5, 2017 at 9:04 AM, Donald Szeto wrote:
> Are you using the appName in engine.json that corresponds to the appId you
> used when you did `pio import`? Setting a new appName in engine.json wil
Are you using the appName in engine.json that corresponds to the appId you
used when you did `pio import`? Setting a new appName in engine.json will
not automatically create a new app. Apps are created when you do `pio app
new`.
On Tue, Apr 4, 2017 at 8:13 PM Vaghawan Ojha wrote:
Hi,
Yes, I cou
Hi,
Yes, I couldn't use different appName. Even when I changed the appName in
engine.json and did pio build, the app name in pio app list still reamins
the same. Something to do with the pio itself, I guess.
Thank you very much for your support.
On Mon, Apr 3, 2017 at 6:58 PM, Pat Ferrel wrote:
Ok, so you are using pio 0.10.0, the UR v 0.5.0 and have disabled the
blacklistEvents as shown below?
Then when you query for a user you are not getting all items returned?
Can you share an example of the query you send to pio and the JSON that is
created for Elasticsearch?
On Apr 4, 2017, a
What version of PIO are you using?
On Apr 3, 2017, at 2:07 PM, infoquest india wrote:
I have done corrections and its giving errors below
ERROR] [Console$] No storage backend implementation can be found (tried both
org.apache.predictionio.data.storage.elasticsearch.ESModels and
elasticsear
Hi,
Sorry my bad, I searched for the piece of code on the internet and your
repository came first. I had the right repo in prod (
https://github.com/actionml/universal-recommender), I doubled check. Sorry
for the misunderstanding.
We still have the same problem.
Here the engine.json we use:
*{*
