You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Michele Riva (JIRA)" <ji...@apache.org> on 2019/07/10 15:12:00 UTC

[jira] [Comment Edited] (UNOMI-238) Unable to create profile with consent info

    [ https://issues.apache.org/jira/browse/UNOMI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882174#comment-16882174 ] 

Michele Riva edited comment on UNOMI-238 at 7/10/19 3:11 PM:
-------------------------------------------------------------

Yes, I am performing a massive import (up to 5.5M users) using Node.js 11 as client.
 I'm spawning 25 workers (Node.js threads) which perform 5 concurrent requests per worker. Unomi is behind an AWS load balancer, so the load is split on different EC2 machines.

Due to the error referenced in the UNOMI-237 Jira, if a POST request fails, I set a retry policy that performs the same POST request with a delay of 1 second, for a maximum of 10 times.

The object I'm inserting looks like this (not using the real keys/values for privacy purposes):

 
{code:java}
{
  itemId: "3792347958023045",
  properties: {
    "foo-bar": "67123012087946927342",
    "customer-id": "513687938109428376497",
    "alternate-customer-id": "62398472340290482",
    status: "foo",
    "customer-type": "recurrent",
    "loyalty-points": 234,
    "loyalty-points-lastupdate": null,
    createDate: null,
    createUser: null,
    lastUpdate: null,
    lastUpdateUser: null,
    birthDate: "1995-01-29",
    gender: "male",
    firstName: "Michele",
    lastName: "Riva",
    addresses: {
      shippingAddress: {
        address: "address-here",
        city: "milan",
        zip: "20100",
        state: "it",
        province: "mi"
      }
    },
    phone: "0000000000",
    email: "email-here",
   "some-service-id": "1623918700203123",
  },
  consents: {
    "foo/policy": {
      scope: "foo",
      typeIdentifier: "policy",
      status: "GRANTED",
      statusDate: "some-status-date",
      revokeDate: "some-revoke-date"
    },
    "foo/contacts": {
      scope: "foo",
      typeIdentifier: "contacts",
      status: "GRANTED",
      statusDate: "some-status-date",
      revokeDate: "some-revoke-date"
    }
  },
  version: 1,
  }
}{code}
Please note that deleting the "consents" property, the import process works fine.
I've tried to be as specific as possible, hope it helps! 


was (Author: micheleriva):
Yes, I am performing a massive import (up to 5.5M users) using Node.js 11 as client.
I'm spawning 25 workers (Node.js threads) which perform 5 concurrent requests per worker. Unomi is behind an AWS load balancer, so the load is split on different EC2 machines.

Due to the error referenced in the UNOMI-237 Jira, if a POST request fails, I set a retry policy that performs the same POST request with a delay of 1 second, for a maximum of 10 times.

The object I'm inserting looks like this (not using the real keys/values for privacy purposes):

 
{code:java}
{
  itemId: "3792347958023045",
  properties: {
    "foo-bar": "67123012087946927342",
    "customer-id": "513687938109428376497",
    "alternate-customer-id": "62398472340290482",
    status: "foo",
    "customer-type": "recurrent",
    "loyalty-points": 234,
    "loyalty-points-lastupdate": null,
    createDate: null,
    createUser: null,
    lastUpdate: null,
    lastUpdateUser: null,
    birthDate: "1995-01-29",
    gender: "male",
    firstName: "Michele",
    lastName: "Riva",
    addresses: {
      shippingAddress: {
        address: "address-here",
        city: "milan",
        zip: "20100",
        state: "it",
        province: "mi"
      }
    },
    phone: "0000000000",
    email: "email-here",
   "some-service-id": "1623918700203123",
  },
  consents: {
    "foo/policy": {
      scope: "foo",
      typeIdentifier: "policy",
      status: "GRANTED",
      statusDate: "some-status-date",
      revokeDate: "some-revoke-date"
    },
    "foo/contacts": {
      scope: "foo",
      typeIdentifier: "contacts",
      status: "GRANTED",
      statusDate: "some-status-date",
      revokeDate: "some-revoke-date"
    }
  },
  version: 1,
  }
}{code}
Please note that deleting the "consents" property, the import process works fine.

 

> Unable to create profile with consent info
> ------------------------------------------
>
>                 Key: UNOMI-238
>                 URL: https://issues.apache.org/jira/browse/UNOMI-238
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.4.0
>            Reporter: Michele Riva
>            Priority: Critical
>
> Hi,
> I'm not able to create a profile including its consents properties.
> If I try to add the "consents" property to the profile, Unomi returns a 500 status code. Looking at the docs, I've seen that the only way to add consents is by posting an event on a given session.
> I currently have millions of profiles to be imported and adding their consent during profile creation would be awesome.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)