Remove mutually exclusive records

By -

What would be the fastest way to remove mutually exclusive record in the record set. I'm using Python and can leverage Pandas if needed.

I have following data:

Record ID Shared On
(UNIX timestamp)		 Share type Share To User
1 1611872850 shared user A
2 1611872851 shared user B
3 1611872852 shared user B
1 1611872853 share_removed user A
3 1611872854 share_removed user B
4 1611872855 shared user C
1 1611872856 shared user A
2 1611872857 share_removed user B
1 1611872858 share_removed user A

As we see that for example, record 1 was shared to user A, then removed from User A, then shared again, and then removed, hence no records should exist.

Output should be only one row:

Record ID Shared On Share type Share To User
4 1611872855 shared user C

One option is to use a dictionary and then remove the record if mutually exclusive record with they key and share type exist in the record. Key might be something like [recordId]-[shareType]-[sharedToUser]

I was thinking maybe there is similar functionality already exists somewhere (in Pandas?)



from Recent Questions - Stack Overflow https://ift.tt/3t8Yxdm
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more