[
https://issues.apache.org/jira/browse/IGNITE-8674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor updated IGNITE-8674:
---------------------------
Summary: LINQ exception with non-default entity sql schema (was:
Ignite.NET LINQ exception with non-default entity sql schema)
> LINQ exception with non-default entity sql schema
> -------------------------------------------------
>
> Key: IGNITE-8674
> URL: https://issues.apache.org/jira/browse/IGNITE-8674
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.4, 2.5
> Environment: Docker 18.03.1 with microsoft/dotnet:2.0-runtime image.
> NET Core 2.0. Ignite 2.5 + Ignite.Linq 2.5 (The same issue for 2.4). JRE
> 8u172. Cache configuration:
>
> CacheConfiguration
> {
> Name = nameof(UserAccount),
> DataRegionName = Constants.DefaultDataRegionName,
> Backups = 1,
> CacheMode = CacheMode.Partitioned,
> WriteThrough = true,
> ReadThrough = true,
> WriteBehindEnabled = true,
> CacheStoreFactory = new StoreFactory<FileStore<Guid,
> UserAccount>>(),
> SqlSchema = "public",
> QueryEntities = new[]
> {
> new QueryEntity(typeof(Guid), typeof(UserAccount))
> }
> };
> Reporter: Victor
> Priority: Critical
>
> Exception in linq query if use non-default - "public" sql schema for cache
> type. I used "public" sql schema in "UserAccount" cache configuration:
> "Apache.Ignite.Core.Common.IgniteException: 'Failed to parse query. Schema
> "UserAccount" not found; SQL statement:
> select _T0._KEY, _T0.EMAIL, _T0.NAME, _T0.PHONE, _T1.BIRTHDAY, _T1.AGE from
> "UserAccount".USERACCOUNT as _T0 inner join "UserProfile".USERPROFILE as _T1
> on (_T1._KEY = _T0._KEY) order by (_T1.AGE) "
> Query works correctly if I not set (use default "UserAccount") schema for
> type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
