Namespace clash with Microsoft.Azure.Cosmos.Table

Describe the bug I’ve a project that references both Microsoft.Azure.Cosmos 3.0.0.9-preview and StreamStone 2.3.0 which in turn has a reference to Microsoft.Azure.Cosmos.Table 1.0.0.0.

One error I encountered is as follows The type 'IndexingMode' exists in both 'Microsoft.Azure.Cosmos.Direct, Version=3.0.0.9, Culture=neutral, PublicKeyToken=31bf3856ad364e35' and 'Microsoft.Azure.Cosmos.Table, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' (CS0433) [deleteme]

This also begs the question, what’s the direction for CosmosDb .NET SDK going forward? Will it be consolidated into Microsoft.Azure.Cosmos or will it be broken down into multiple parts? (core/direct?, document/sql, mongo api, cassandra api, table api, gremlin api)?

To Reproduce

1. dotnet new xunit
2. dotnet add package Microsoft.Azure.Cosmos -v 3.0.0.9-preview
3. dotnet add package StreamStone -v 2.3.0
4. use code below

using System;
using Xunit;
using Microsoft.Azure.Cosmos;

namespace deleteme
{
    public class UnitTest1
    {
        [Fact]
        public void Test1()
        {
            var x = new IndexingPolicy
            {
                IncludedPaths = { new IncludedPath{Path=""}},
                IndexingMode = Microsoft.Azure.Cosmos.IndexingMode.Lazy // uh, oh
            };
        }
    }
}

Environment summary SDK Version: 2.2.505 MacOS Mojave

[PaulCheng]

There is no need to update existing storage account or cosmosdb table account. Emulator will continue working as well.

[donghexu]

@PaulCheng