Community
Participate
Working Groups
If the query definition contains evaluation backend hints (see https://www.eclipse.org/viatra/documentation/query-language.html#_pattern_structure ) to select Local Search backend (with "search"), it always uses the EMF-specific LS backend, even if the Generic LS backend is selected with engine level hints. Example: search pattern className(c : EClass, clName : java ^java.lang.String) { EClass.name(c, clName); } queryOptions = LocalSearchHints.getDefaultGeneric() .setUseBase(true).build(); queryEngineOptions = ViatraQueryEngineOptions .defineOptions().withDefaultHint(queryOptions) .withDefaultBackend(queryOptions.getQueryBackendFactory()).build(); engine = AdvancedViatraQueryEngine.createUnmanagedEngine(scope, queryEngineOptions); Creating the matcher will NOT use Generic LS backend.
New Gerrit change created: https://git.eclipse.org/r/122509
New Gerrit change created: https://git.eclipse.org/r/122668
Gerrit change https://git.eclipse.org/r/122509 was merged to [master]. Commit: http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=0a74f79bf57b94d3ee0155479645180ae710e8e0
Gerrit change https://git.eclipse.org/r/122668 was merged to [master]. Commit: http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=f144a1093376c42dd2c2c83af9ba9993bb52b140
Fixed in master.