Cannot find symbol IMMEDIATE

utkarsh · March 26, 2019, 12:05pm

code in v2.3.3
IndexResponse idxResp=getIndex().setId(documentDto.getId().toString()).setSource(source).setRefresh(true).execute().actionGet();
While upgrading from ES v2.3.3 to ES v5.6.2, I am facing the error: "Could not resolve symbol : variable IMMEDIATE" at the following line of code-
code for v5.6.2-
IndexResponse idxResp=getIndex().setId(documentDto.getId().toString()).setSource(source).setRefresh(IMMEDIATE).execute().actionGet();

I have even tried setRefreshPolicy(RefreshPolicy.IMMEDIATE), but it didn't work.
Please Help.

dadoonet · March 26, 2019, 1:06pm

What do you mean by "it did not work"?

BTW you should move to the Rest Client as the TransportClient is now deprecated.
Also, I'd recommend using the latest 5.x version or event better move to 6.x...

utkarsh · March 26, 2019, 1:47pm

By it did not work, I mean that the error "IMMEDIATE variable could not be found" still persists even after using setRefrreshPolicy(RefreshPolicy.IMMEDIATE).
During initial upgrades I was trying with Rest client but then I was facing some issue so I decided to stay with Transport client as suggested by Tim Vernum in this post-

dadoonet · March 26, 2019, 2:04pm

Is it a compilation problem or happening at runtime ?

Asking that because I can see this Enum here:

github.com

elastic/elasticsearch/blob/5.6/core/src/main/java/org/elasticsearch/action/support/WriteRequest.java#L73




enum RefreshPolicy implements Writeable {
    /**
     * Don't refresh after this request. The default.
     */
    NONE("false"),
    /**
     * Force a refresh as part of this request. This refresh policy does not scale for high indexing or search throughput but is useful
     * to present a consistent view to for indices with very low traffic. And it is wonderful for tests!
     */
    IMMEDIATE("true"),
    /**
     * Leave this request open until a refresh has made the contents of this request visible to search. This refresh policy is
     * compatible with high indexing and search throughput but it causes the request to wait to reply until a refresh occurs.
     */
    WAIT_UNTIL("wait_for");


    private final String value;


    RefreshPolicy(String value) {
        this.value = value;

So you should be able to access to WriteRequest.RefreshPolicy.IMMEDIATE.

Also

.setRefreshPolicy("true")

Should have the same effect.

utkarsh · March 27, 2019, 8:47am

It was a compile time error and yes this has been resolved by using .setRefreshPolicy("true").
Thank you very much for your time and effort.

system · April 24, 2019, 8:47am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.