wonderful-toddler-56821
01/20/2023, 1:02 AMwonderful-toddler-56821
01/20/2023, 1:04 AMhelpful-truck-5495
01/20/2023, 2:54 AMfull-cat-91667
01/20/2023, 8:23 AMbusy-portugal-18769
01/20/2023, 9:54 AMmammoth-energy-40257
01/20/2023, 11:34 AMmost-iron-23985
01/20/2023, 5:09 PMquiet-insurance-54953
01/20/2023, 6:46 PMfancy-answer-79663
01/21/2023, 12:43 PMERROR router.WEBHOOK.network router/network.go:136 400 Unable to construct "POST" request for URL : "192.168.201.223:30808/contentListener"
rudderstack is deployed on kubernetes. The end point is ok. I could send events to it by postman.fancy-answer-79663
01/22/2023, 1:21 PMrough-refrigerator-26314
01/22/2023, 8:18 PMProduct Added
and a v2 for Product Added
) in my tracking plan.
This is helpful when:
• Trying to rollout an update to an event’s schema to a dev environment while not effecting prod.
• Allow for breaking changes to event’s schemas without requiring the event to be refactored everywhere is it implemented in the application code. Some events can be validated against v1 and others against v2 of the schema.
I know this is possible in Segment but can’t find anything similar in Rudderstack. Maybe I am missing it in the Rudderstack docs or Tracking Plan API docs in postman.full-jewelry-19589
01/23/2023, 5:13 AMflaky-ability-44647
01/23/2023, 12:37 PMambitious-engineer-11304
01/23/2023, 12:43 PMbrash-nightfall-83618
01/24/2023, 10:17 AMfancy-answer-79663
01/24/2023, 11:32 AMstraight-raincoat-91897
01/24/2023, 12:12 PMambitious-diamond-50119
01/24/2023, 12:24 PMarn:aws:iam::422074288268:user/s3-copy
but I could not attached it to my S3 bucket and getting this error Invalid principal in policy
chilly-vase-86922
01/24/2023, 8:40 PMTo filter the destinations, you need to specify the exact destination names. To get these names, you can go to the RudderStack directory.Where exactly in that directory can I see these names? There used to be a list of names in the documentation (which I had linked to from our code), but that's no longer there. Is there no public documentation that can be referenced? Is it just the name of each item listed under the Destinations tab at https://app.rudderstack.com/directory? e.g.
Google Adwords Remarketing Lists (Customer Match)
or Customer IO
(not to be confused with the Customerio
event stream, or the <http://Customer.io|Customer.io>
cloud extract)most-ocean-90575
01/25/2023, 5:19 AMHi team,
most-ocean-90575
01/25/2023, 5:20 AMfull-cat-91667
01/25/2023, 5:40 AMbig-market-92547
01/25/2023, 5:42 AMambitious-diamond-50119
01/25/2023, 6:59 AMbig-market-92547
01/25/2023, 11:14 AMfuture-nest-36254
01/25/2023, 11:26 AMmodern-optician-88980
01/25/2023, 1:14 PMable-controller-17526
01/25/2023, 9:13 PMuuid_ts
, timestamp
, sent_at
, received_at
and loaded_at
This is all coming from the same Javascript SDK source. In the `tracks`table of almost 21k rows only 54 rows were duplicated when partitioning by id
, so this made me wonder about the following.
The only values not duplicated are the shown in the screenshot.
So my questions are:
1. In which conditions can the event be loaded a day later? Can it happen on a timeframe longer than one day?
2. Is it safe to just partition by id
, order by sent_at
ascending and then take the first value there?
a. If not which column is it recommended to use to order by
when partitioning in order to actually deduplicate? (from these uuid_ts
, timestamp
, sent_at
, received_at
and loaded_at
)
3. Shouldn't the timestamps
also be equal? I mean we are talking milliseconds of difference here, but I thought the formula described in the docs would account for that.
a. If they shouldn't be the same, what does this difference signify?
4. What other strategy for deduplication is recommended on the warehouse if this is not the way?
Thanks for the helpfew-farmer-52883
01/26/2023, 2:55 AMpage
calls in device-mode. I see it's not possible right now as client-side filtering only filters track
calls? Any alternatives I can use to achieve this? Thanks.incalculable-pizza-92915
01/26/2023, 5:37 AM@rudderstack/rudder-sdk-react-native
but got some complaints regarding async-lock
. Tried both ^1.1.2
and 1.6.0
but got the same issue. (error message attached)
Our last attempt to build with @rudderstack/rudder-sdk-react-native: v1.1.2
is successful. That was last January 05, 2023. Thanks!